Upgrade to Node 16 #2218
Merged
Upgrade to Node 16 #2218
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
Member
naltatis
commented
Jan 6, 2022
naltatis
commented
- upgrade to Node 16
- removed npm-force-resolutions
naltatis
changed the title
|
Hatten wir hier nicht das Problem, dass keine Diffs mehr in der package-lock.json möglich waren? |
Doch das funktioniert. Das package-lock.json Format hat sich nur bei v16 verändert. Heißt es ist wichtig, dass alle dann auch node 16 verwenden. Das ist aber kein Problem. |
|
Please be aware that npm 8 changes the behavior for update: npm/cli#708 |
dontbyte
pushed a commit
to dontbyte/evcc
that referenced
this pull request
Aug 2, 2022
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.