Package Lock Refresh and Update #187
Draft
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
Tbaile
force-pushed
the
refresh-package-lock
branch
from
ee8eddc to
49f4881
Compare
4 tasks
andre8244
approved these changes
Feb 13, 2023
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.
Due to building issues with node up to date LTS versions, I've downgraded the package-lock to v1 to match the shipped
npmfor node14.Updated
Containerfileto node 14 and now using thenpm cicommand to install packages.Please test this thoroughly due to unknown possible changes in the packages (they shouldn't be any, but you never know)
Edit ee8eddc : I've ignored the base configuration file from the build, I don't think it belongs inside a production-ready environment. Please feel free to prove me wrong and/or make me know that breaks something in the currently running systems.