Set package dependencies to fixed versions and npm audit fix#407
Merged
Conversation
ShiningTrapez
approved these changes
Sep 29, 2025
ShiningTrapez
requested changes
Sep 29, 2025
ShiningTrapez
left a comment
ShiningTrapez
left a comment
Contributor
There was a problem hiding this comment.
This appears to break the dependency resolution
ShiningTrapez
approved these changes
Sep 29, 2025
markhouldridge
changed the title
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
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.
📺 What
package-lock.jsonfollowingnpm audit fixfixing a critical issue withform-datawhich may be exploited to forge or intercept multipart data.rollup-plugin-visualizeras this does not appear to be used by rollup config and was breaking the builds.🛠 How
package.jsonnpm audit fixto fix critical issue in dependency graph.