Update to use Node 20 and update dependencies to address vulnerabilities #173
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
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 PR addresses all vulnerabilities that have been flagged over the past several months by Dependabot, see https://github.com/GoogleChromeLabs/wpp-research/pulls/app%2Fdependabot.
Doing this in one PR is simpler as it avoids all the merge conflicts from
package.jsonandpackage-lock.json. Additionally, we were still requiring the use of outdated Node 18 in.nvmrcwhich was preventing some dependencies from updating to the latest version, so this PR also updates it to the widely used Node 20.I've run all of our commands to verify they still work as before, so I don't think these updates are causing any unexpected issues.