Add overrides for dev dependencies with critical vulnerabilities #1012
Conversation
This file contains hidden or 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
ajivanyandev
approved these changes
Nov 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Practical Value
Eliminating dependencies with critical vulnerabilities as quickly as possible.
Details
form-data: comes fromlernaandwait-on. I added an override for theform-dataversion since I skipped updating lerna this time, but I believe the override may become unnecessary oncelernais updated or removed (after migrating topnpm/nx)@babel/traverse: comes frombabel-eslint(dependency removed in the PR) andjest@29. I was unable to update tojest@30, becausejest-image-snapshothas a peer dependency onjest@<=29and is not updated anymore, so I added an override for the@babel/traverseversionProblematic Dependencies
jest-image-snapshot