Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Npm v5.0.0 released

blog.npmjs.org

Post reply on HN
Print view View original

21–30 of 117 posts

Re: Npm v5.0.0 released

#22

Post by nailer »

chrisweekly wrote: post #10

First 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

Calling npm 'the naked emperor' for not implementing something it did, infact, implement is uncalled for.

Edit: added links in response to unexplained downmods. The parent is simply, provably wrong.

Re: Npm v5.0.0 released

#23

Post by shadowmint »

This might be a totally stupid question, but what does that mean?

    npm install npm@latest -g

    /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
    /usr/local/lib
    └── npm@4.6.1
How do I install it? Or... it's not quite released yet after all?

Edit: nevermind, I found it --> https://github.com/npm/npm/releases this is the 'prerelease' release.

Re: Npm v5.0.0 released

#24

Post by nailer »

k__ wrote: post #15

Someone told they now use hashes for versioning, like Nix, is this true? Is it finally save to install 2 times and get 100% the same packages?

It's been that way for years, since shrinkwrap was invented.

Re: Npm v5.0.0 released

#25

Post by Thomaschaaf »

shadowmint wrote: post #23

This might be a totally stupid question, but what does that mean? npm install npm@latest -g /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js /usr/local/lib └── npm@4.6.1 How do I install it? Or... it's not quite released yet after all? Edit: nevermind, I found it --> https://github.com/npm/npm/releases this is the 'prerelease' release.

  npm install npm@next -g
works :)

Re: Npm v5.0.0 released

#26

Post by josteink »

cheapsteak wrote: post #20
pluma wrote: post #16

Earlier quoted context omitted.

When io.js merged back into node.js the following happened: 1. Node.js was abandoned and replaced with io.js. 2. Io.js was relabelled as node.js. 3. The node.js project was put under open governance via the creation of the Node Foundation. This doesn't really compare to npm: * The npm-cli's name is using npm Inc's trademark: giving it away would leave the company with no name or create unwanted ambiguity between npm…

>resolved by dropping npm-cli from the official releases. But that would break 7 years of documentation and tutorials, likely bad for newcomers and thus the ecosystem

Not to mention quite a few CI build pipelines.

Re: Npm v5.0.0 released

#27

Post by nailer »

shadowmint wrote: post #23

This might be a totally stupid question, but what does that mean? npm install npm@latest -g /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js /usr/local/lib └── npm@4.6.1 How do I install it? Or... it's not quite released yet after all? Edit: nevermind, I found it --> https://github.com/npm/npm/releases this is the 'prerelease' release.

Right now latest still points to v4. You can install 5 with:

    npm install -g npm@5
Then see:

    npm -g ls npm
Which returns:

    +-- npm@5.0.0

Re: Npm v5.0.0 released

#29

Post by vacri »

How is the package manager for a language still iterating through major versions and making breaking changes nearly a decade after launch? Node is bizarre in that you have to follow its package manager so closely.

Re: Npm v5.0.0 released

#30

Post by gear54rus »

Achshar wrote: post #9

So 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?

Post reply on HN