NPM v4.0.0

#1

Post by Jarlakxen » Sun, Oct 23, 2016, 1:50 AM UTC

Re: NPM v4.0.0

#2

Post by Lx1oG-AWb6h_ZG0 » Sun, Oct 23, 2016, 4:34 AM UTC

I'm glad for the relatively low amount of breaking changes this time. npm prepare should be a nice addition (using prepublish for, e.g., installing typings is such a non obvious hack).

That said, I'm still not certain about shrinkwrap excluding dev deps. I mainly use it to ensure my build agent uses the same dependencies as my dev box, and at a time when things like babel pull in a ridiculous amount of sub dependencies, it really does not make sense to not lock down _all_ your dependencies by default.

Re: NPM v4.0.0

#3

Post by gableroux » Sun, Oct 23, 2016, 4:35 AM UTC

npm search will at least return results now ahah. I didn't know about https://npm.im/npms-cli , sounds like a great alternative. Thanks for sharing this release here :)

Re: NPM v4.0.0

#4

Post by madeofpalk » Sun, Oct 23, 2016, 5:17 AM UTC

Lx1oG-AWb6h_ZG0 wrote: post #2

I'm glad for the relatively low amount of breaking changes this time. npm prepare should be a nice addition (using prepublish for, e.g., installing typings is such a non obvious hack). That said, I'm still not certain about shrinkwrap excluding dev deps. I mainly use it to ensure my build agent uses the same dependencies as my dev box, and at a time when things like babel pull in a ridiculous amount of sub dependenci…

The difference between regular dependencies and devDependencies is very blurry with things like Webpack and Babel - they're not required at runtime but they're responsible for significant amounts of runtime.

Luckily, npm shrinkwrap accepts a --dev option to include devDependencies

Re: NPM v4.0.0

#5

Post by octref » Sun, Oct 23, 2016, 5:40 AM UTC

After 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 actually fixing the tab completion, which has been slow and broken forever?

Re: NPM v4.0.0

#6

Post by scrollaway » Sun, Oct 23, 2016, 5:44 AM UTC

octref wrote: post #5

After 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

Re: NPM v4.0.0

#7

Post by octref » Sun, Oct 23, 2016, 5:50 AM UTC

scrollaway wrote: post #6

octref wrote: post #5

After 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

Yeah I wouldn't use it in production until it becomes more stable. However the team behind it seems to iterate really fast. Look at the issues fixed between public release and 0.16[0], which is only 7 days.

[0]: https://github.com/yarnpkg/yarn/releases/tag/v0.16.0

Re: NPM v4.0.0

#8

Post by andrewvijay » Sun, Oct 23, 2016, 5:51 AM UTC

Are the NPM guys working on a parallel download feature to speed things up? Have they even noted it as a feature to be implemented? Speed and pkg locking are the only two features that make me use yarn. If they were in npm then most people wont worry about yarn at all I guess.

Re: NPM v4.0.0

#9

Post by amasad » Sun, Oct 23, 2016, 6:04 AM UTC

octref wrote: post #7

scrollaway wrote: post #6

Earlier quoted context omitted.

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

Yeah I wouldn't use it in production until it becomes more stable. However the team behind it seems to iterate really fast. Look at the issues fixed between public release and 0.16[0], which is only 7 days. [0]: https://github.com/yarnpkg/yarn/releases/tag/v0.16.0

I've been using it in production for a large app for the past week and it's been great. CI is faster, deploying is faster and dev is faster.

Re: NPM v4.0.0

#10

Post by kolme » Sun, Oct 23, 2016, 8:00 AM UTC

> npm scripts no longer prepend the path of the node executable used to run npm before running scripts. A --scripts-prepend-node-path option has been added to configure this behavior.

Why? That seems like a good default, something most people would need.