> npm's default git branch is no longer `master`. We'll be using `latest` from now on. Is there any reason to do this?
NPM v4.0.0
21–30 of 57 posts
Re: NPM v4.0.0
#22Earlier quoted context omitted.
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is. /rant Thanks for the highlight, I use npm solely for global installs, will…
> Before praising something, makes sense to tell people what it is. I don't know where you've been but anyone who is even remotely invested in the npm ecosystem probably knows what Yarn is at this point.
Re: NPM v4.0.0
#23After using yarn for a week, I can't imagine going back to npm. I use npm 90% for install, and yarn does this so much better. Installs are 3-4 times faster. Output is minimal and readable (compared to npm's wall of text that I never read). Packages are cached so I can work with slow connections in coffee shops. Sorry to be blunt, but I feel none of the release features gonna help my daily usage of npm. How about actu…
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is. /rant Thanks for the highlight, I use npm solely for global installs, will…
And DuckDuckGo (mentioned twice in the comment) is relevant because?
Re: NPM v4.0.0
#24Earlier quoted context omitted.
> Before praising something, makes sense to tell people what it is. I don't know where you've been but anyone who is even remotely invested in the npm ecosystem probably knows what Yarn is at this point.
This is irrelevant. You may be just a new comer, or not a professional developer, and still want to use yarn. A clear website seems a basic requirement to me for any project.
Well, you can't always depend on that, and in the end of the day, nothing beats actually researching and asking around.
The GNU tools have some of the worst webpages -- and yet they are some of the most useful, and commonly used, packages.
Re: NPM v4.0.0
#25NPM is so Oct 10 2016.
Re: NPM v4.0.0
#26Earlier quoted context omitted.
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is. /rant Thanks for the highlight, I use npm solely for global installs, will…
> I went to DuckDuckGo to check out what yarn is. And DuckDuckGo (mentioned twice in the comment) is relevant because?
Re: NPM v4.0.0
#27Earlier quoted context omitted.
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is. /rant Thanks for the highlight, I use npm solely for global installs, will…
Yarn has been the talk of the dev world for the last week man. It had a large upswing on both here and reddit.
Re: NPM v4.0.0
#28After using yarn for a week, I can't imagine going back to npm. I use npm 90% for install, and yarn does this so much better. Installs are 3-4 times faster. Output is minimal and readable (compared to npm's wall of text that I never read). Packages are cached so I can work with slow connections in coffee shops. Sorry to be blunt, but I feel none of the release features gonna help my daily usage of npm. How about actu…
I'm super excited to use yarn but, just a heads up, we hit this pretty severe issue when setting it up for our projects: https://github.com/yarnpkg/yarn/issues/761
I wouldn't want 1 tool to rule them all, but a single tooling/dev/task kit and a single dependency/pckg manager would be nice.
Re: NPM v4.0.0
#29Earlier quoted context omitted.
This is irrelevant. You may be just a new comer, or not a professional developer, and still want to use yarn. A clear website seems a basic requirement to me for any project.
> A clear website seems a basic requirement to me for any project. Well, you can't always depend on that, and in the end of the day, nothing beats actually researching and asking around. The GNU tools have some of the worst webpages -- and yet they are some of the most useful, and commonly used, packages.
1. https://www.gnu.org/software/tar/ 2. https://gnu.io/social/
Re: NPM v4.0.0
#30After using yarn for a week, I can't imagine going back to npm. I use npm 90% for install, and yarn does this so much better. Installs are 3-4 times faster. Output is minimal and readable (compared to npm's wall of text that I never read). Packages are cached so I can work with slow connections in coffee shops. Sorry to be blunt, but I feel none of the release features gonna help my daily usage of npm. How about actu…
I went to DuckDuckGo to check out what yarn is. The front page makes no mention of JavaScript at all (at least on mobile). Accordingly to DuckDuckGo the whole site mentions "JavaScript" only three times. The same is true about the GitHub readme: no mentions of JavaScript at all. Before praising something, makes sense to tell people what it is. /rant Thanks for the highlight, I use npm solely for global installs, will…