MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/javascript/comments/6e9hix/node_800_released/dia39t3/?context=3
r/javascript • u/jcready __proto__ • May 30 '17
56 comments sorted by
View all comments
Show parent comments
7
The biggest deal I see in this is defaulting to npm 5, which brings a majority of the features yarn was introduced for.
Actual node devs might say the async stuff is a big deal, I personally can't comment on that.
Other than that it just seems like a proper major release, with some cleanups here and there, new deprecations, the usual stuff.
1 u/djslakor May 31 '17 edited May 31 '17 Yarn is still quite a bit faster. We don't see any reason to transition back to npm. In fact, @maybekatz who works on NPM5 just recently did a PR for yarn that made it even faster. :)Async is a big deal, but it was in 7.x, too. 2 u/Akkuma May 31 '17 Yarn isn't that much faster based on benchmarks I've seen, https://github.com/JamieMason/npm-cache-benchmarkBased on that it is negligible and semver versioning of git dependencies in npm5 is way sweeter than a few less seconds. 0 u/djslakor May 31 '17 I've used it in production. Every day when I update our yarn.lock/package-lock.json, I see how long it takes. Not benchmarks.
1
Yarn is still quite a bit faster. We don't see any reason to transition back to npm. In fact, @maybekatz who works on NPM5 just recently did a PR for yarn that made it even faster. :)
Async is a big deal, but it was in 7.x, too.
2 u/Akkuma May 31 '17 Yarn isn't that much faster based on benchmarks I've seen, https://github.com/JamieMason/npm-cache-benchmarkBased on that it is negligible and semver versioning of git dependencies in npm5 is way sweeter than a few less seconds. 0 u/djslakor May 31 '17 I've used it in production. Every day when I update our yarn.lock/package-lock.json, I see how long it takes. Not benchmarks.
2
Yarn isn't that much faster based on benchmarks I've seen, https://github.com/JamieMason/npm-cache-benchmark
Based on that it is negligible and semver versioning of git dependencies in npm5 is way sweeter than a few less seconds.
0 u/djslakor May 31 '17 I've used it in production. Every day when I update our yarn.lock/package-lock.json, I see how long it takes. Not benchmarks.
0
I've used it in production. Every day when I update our yarn.lock/package-lock.json, I see how long it takes. Not benchmarks.
7
u/MildlySerious May 31 '17
The biggest deal I see in this is defaulting to npm 5, which brings a majority of the features yarn was introduced for.
Actual node devs might say the async stuff is a big deal, I personally can't comment on that.
Other than that it just seems like a proper major release, with some cleanups here and there, new deprecations, the usual stuff.