Modify package.json to retain all dependencies' version, not allowing…#733
Merged
minhsueh merged 2 commits intomaterialsproject:mainfrom Sep 26, 2025
Merged
Conversation
added 2 commits
September 25, 2025 17:15
… compatibility, as we are using Node 12; there are too many compatibility issues.
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
1 participant
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.
Pins all runtime/dev dependency versions in package.json.
We’re still on Node 12, and newer transitive releases (e.g., packages using node: imports or optional chaining) keep breaking CI/local runs.
Tagging @tschaume , as discussed, a full Node upgrade is the better long-term fix, but this pins the tree to keep us stable in the meantime.