Repository navigation
馃彈 nodejs 24 caused package-lock.json change - #40444
Merged
Merged
Conversation
danielrozenberg
approved these changes
Dec 1, 2025
powerivq
force-pushed
the
pac
branch
3 times, most recently
from
December 1, 2025 18:48
9167681 to
33e1bd9
Compare
danielrozenberg
approved these changes
Dec 1, 2025
danielrozenberg
left a comment
danielrozenberg
left a comment
Member
There was a problem hiding this comment.
Reapproving to skip bundle-size check
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
3 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.
Nodejs 24 is generating some new fields on package-lock.json, causing PR builds to fail. Updating the lock file.