Respect package-lock.json when building the frontend with init-deployment.sh #663
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This updates the init-deployment.sh script so that it copies the frontend's package-lock.json file into the build context. The command "npm install" is replaced with "npm ci", which will do a "clean install" of the exact versions in package-lock.json and will fail if anything breaks. Closes #662
jkglasbrenner
added
bug
Closed
Closed
|
Several people on our team tested this out and confirmed it worked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the init-deployment.sh script so that it copies the frontend's package-lock.json file into the build context. The command "npm install" is replaced with "npm ci", which will do a "clean install" of the exact versions in package-lock.json and will fail if anything breaks.
Closes #661, #662