Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package lock for NPM #11

Closed
Download opened this issue Jul 3, 2017 · 3 comments
Closed

Package lock for NPM #11

Download opened this issue Jul 3, 2017 · 3 comments

Comments

@Download
Copy link
Owner

Download commented Jul 3, 2017

@minecrawler see #4 and #9

@Download Download added this to the Add minecrawler as collaborator milestone Jul 3, 2017
@Download
Copy link
Owner Author

Download commented Jul 3, 2017

You should explain me how this works sometimes. I guess it locks the versions right?

@minecrawler
Copy link
Collaborator

minecrawler commented Jul 3, 2017

It's a NPM@5 feature (probably added in response to yarn). Basically, as a developer, you npm i . the dependencies, make the source code work, and then distribute the source with the lock file. Anyone installing the package after that with npm i mics will get the exact dependency versions as described in the lock file. That way, the runtime environment will reflect the one which was used by the developer, so the probability of it working is very high. The dependencies can be updated by running npm update . or npm i . in the package root, the new versions will then be reflected in the lockfile.

For more information, please refer to the official docs.

@Download
Copy link
Owner Author

Download commented Jul 3, 2017

Great stuff! Thanks for the explanation. 👍

Download added a commit that referenced this issue Jul 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants