Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    You already stated the reason: "This allows for strong reproductibility: you always know what is built from what." Commented Jul 13, 2020 at 14:51
  • Can you be sure that every library you are linking to is using semantic versioning? Or could it be a made-up versioning scheme that happens to look similar to semver. What would you prefer as a pinning behavior for the second kind of versioning? Commented Jul 13, 2020 at 14:54
  • By default npm install currently uses ^x.y.z in package.json, i.e. x.y.z up to but not including x+1.0.0 - that is pinning the major version. It's package-lock.json that stores the exact versions of everything in the dependency tree, but you do not necessarily have to use that. Commented Jul 13, 2020 at 15:00