Earlier quoted context omitted.
It's been that way for years, since shrinkwrap was invented.
Really? Does shrinkwrap work for transitive deps?
Yes, this is a huge selling point to the usefulness of npm-shrinkwrap.
Npm v5.0.0 released
41–50 of 117 posts
Re: Npm v5.0.0 released
#42I'm not able to update it to v5. npm install npm@latest -g doesn't update.
npm install npm@5 -g. Latest still points at 4.x currently.
Re: Npm v5.0.0 released
#43I'm not able to update it to v5. npm install npm@latest -g doesn't update.
[deleted]
Re: Npm v5.0.0 released
#44Earlier quoted context omitted.
Really? Does shrinkwrap work for transitive deps?
Yes, this is a huge selling point to the usefulness of npm-shrinkwrap.
Interesting. I thought yarn and ied were created because this didn't work with npm.
-- edit --
Seems that npm shrikwrap -> npm i -> npm shrikwrap is not guaranteed to produce the same output.
Re: Npm v5.0.0 released
#45So happy with the --save by default. Someone at work kept installing new dependencies without save (they didn't knew about it, somehow). We then had an unusable package.json. I had to manually find directories in node_modules and install them on production -_-.
And I think this is a complete bs. I have to try the module and then make a conscious decision to use (save) it, not kind of save it first and then hope that it actually does what I want. Like wtf, who thought that saving something you download maybe for the first time as a dependency is a good idea?
Most of the time when I do npm install it's for stuff I know I will need. If you want to check something out you can always just --no-save it.
Re: Npm v5.0.0 released
#46First of all: Thank you, yarn, for helping the community see the naked emperor. Deterministic builds by default are such an obvious (in retrospect) core requirement. Couple questions: Question 1: Does anyone else who's been around more than a couple years share my view that Yarn : NPM :: IO.JS : Node? IOW: healthy competition, catalyst for necessary change, ultimately a bridge or stopgap. Question 2: Any good compreh…
> Thank you, yarn, for helping the community see the naked emperor. Deterministic builds by default are such an obvious (in retrospect) core requirement. https://docs.npmjs.com/cli/shrinkwrap provides deterministic builds and has been around far longer than yarn. Since Oct 2014 npm v3 started automatically updating shrinkwrap whenever '--save' was used. See https://github.com/npm/npm/pull/4918#issuecomment-61344871 C…
I personally had invalid dependencies generated with shrinkwrap which did not work with a "npm install" after and had to edit the file manually so I would say it's not yet there.
Re: Npm v5.0.0 released
#47Its still not as fast as yarn FYI.
Yarn doesn't support all of npm's features. At least not as of a couple months ago when it 1) didn't support one of our needs at all, and 2) broke a couple NPM packages on install. This may or may not be part of why it's faster: it does less.
Re: Npm v5.0.0 released
#48It is not NPM, it is npm.
This is good point as it's the third element in their "breaking changes"
> npm will now scold you if you capitalize its name. seriously it will fight you.
Re: Npm v5.0.0 released
#49First of all: Thank you, yarn, for helping the community see the naked emperor. Deterministic builds by default are such an obvious (in retrospect) core requirement. Couple questions: Question 1: Does anyone else who's been around more than a couple years share my view that Yarn : NPM :: IO.JS : Node? IOW: healthy competition, catalyst for necessary change, ultimately a bridge or stopgap. Question 2: Any good compreh…
npm would need to add the --flat option for it to work for me
Re: Npm v5.0.0 released
#50Its still not as fast as yarn FYI.
Yarn doesn't support all of npm's features. At least not as of a couple months ago when it 1) didn't support one of our needs at all, and 2) broke a couple NPM packages on install. This may or may not be part of why it's faster: it does less.
what are these npm's features that yarn doesn't support?