You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior
npm modules are installed via version specified in the package.json, where when installed with yarn, the version are taken from the yarn lock file. This is the normal behaviour with npm lower than version 5.
When installed with npm, the versions can vary between developers and this causes unexpected errors.
Expected behavior
It should install a locked version number. This is possible with npm 5 and the npm lock file, which is similar to yarn.
Minimal reproduction of the problem with instructions
No specific case, but happened to me with the TypeScript version.
What is the motivation / use case for changing the behavior?
Less unexpected errors
Please tell us about your environment:
macOS
The text was updated successfully, but these errors were encountered:
renestalder
changed the title
Add npm lock file für npm 5
Add npm lock file for npm 5
Jul 4, 2017
I'm submitting a ...
Current behavior
npm modules are installed via version specified in the package.json, where when installed with yarn, the version are taken from the yarn lock file. This is the normal behaviour with npm lower than version 5.
When installed with npm, the versions can vary between developers and this causes unexpected errors.
Expected behavior
It should install a locked version number. This is possible with npm 5 and the npm lock file, which is similar to yarn.
Minimal reproduction of the problem with instructions
No specific case, but happened to me with the TypeScript version.
What is the motivation / use case for changing the behavior?
Less unexpected errors
Please tell us about your environment:
macOS
The text was updated successfully, but these errors were encountered: