docs(npm-view): clarify object property access syntax #8795
+16
−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
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 improves the documentation for
npm viewto clarify how to access object properties, particularly when dealing with special characters or numeric keys.Changes
npm view express "time[4.17.1]"npm view [email protected] timeContext
Users were confused about the correct syntax for accessing object properties in
npm viewoutput, especially for thetimefield which maps version numbers to publish dates. The existing example used single quotes in an unclear way (time'[4.8.0]'), and the documentation didn't explain the quoting requirements or provide working examples for common use cases.Closes #5526