We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you for contributing to this project!
Packages are static between deployments and updated manually. However it looks like they're updated to newer versions.
It was noticed that package-lock.json is ignored and not included in the builds. This file is needed to ensure the versions are predictable/static.
The text was updated successfully, but these errors were encountered:
Fixes tl-its-umich-edu#1527 npm is not considering package-lock.json
d0f9d23
Fixes #1527 npm is not considering package-lock.json (#1528)
1498826
Tested a couple packages in Package-lock.json downloaded/used in Myla Beta
:/code/node_modules/@apollo/client$ cat version.js export var version = '3.5.10';
2. D3 version:
:/code/node_modules/d3$ cat package.json { "name": "d3", "version": "7.6.1",
Test passes
Sorry, something went wrong.
jonespm
Successfully merging a pull request may close this issue.
Thank you for contributing to this project!
Expected behavior (A description of what you expected to happen) :
Packages are static between deployments and updated manually. However it looks like they're updated to newer versions.
Additional context (Add any other context about the problem here) :
It was noticed that package-lock.json is ignored and not included in the builds. This file is needed to ensure the versions are predictable/static.
The text was updated successfully, but these errors were encountered: