docs(package-lock-json): clarify version field may be omitted #8800
+2
−0
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
…r certain dependencies
owlstronaut
approved these changes
Dec 1, 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.
Description
This PR clarifies that the
versionfield inpackage-lock.jsondependency objects may be omitted in certain cases.Changes
versionfield is not always presentdev,optional,peer) without aversionfieldContext
Users discovered that some dependency objects in
package-lock.jsondon't include aversionfield (e.g., optional peer dependencies), but the documentation stated thatversionis always present. This caused confusion when tools tried to parse these lockfiles. The example from the issue showed entries with only"dev": true, "optional": true, "peer": truefields.Closes #4796