This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
chore: use npm 8 across projects #2352
Merged
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
ematipico
force-pushed
the
chore/use-npm-8
branch
from
8833dc0
to
d1f6b08
Compare
Deploying with
|
| Latest commit: |
d1f6b08
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e852674a.tools-8rn.pages.dev |
leops
approved these changes
Apr 5, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
This PR forces
enginesto usenpm8. We have had issues so far where the lock files were wrong due to contributors using different versions of npm.Test Plan
Current CI. Checked locally that the website correctly builds