Property: name #3
Merged
Conversation
This file contains 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
added 2 commits
September 13, 2023 16:02
darcyclarke
reviewed
Jan 2, 2024
darcyclarke
approved these changes
Jan 2, 2024
|
Before I merge this I'm going to reintroduce some of the content from 30456e3 👍 |
wesleytodd
approved these changes
Feb 9, 2024
Co-authored-by: Wes Todd <wes@wesleytodd.com>
ljharb
reviewed
Feb 12, 2024
wesleytodd
reviewed
Feb 12, 2024
rotu
pushed a commit
to rotu/package-json-research
that referenced
this pull request
Aug 22, 2024
* npm name field research * add todo issue link * remove install behavior details * include platform specific research * Update research/name.md Co-authored-by: Wes Todd <wes@wesleytodd.com> * . * wip annotations * add sources section back * complete annotations --------- Co-authored-by: Wes Todd <wes@wesleytodd.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Research for the
namefield.I could not find any documentation for unique behavior regarding this field in alternative tools (yarn, pnpm, bun, etc.). If anyone can think of something now please share and I'll update before we land this. Otherwise, the document can always be amended in the future!
Also includes a section on the Scope concept. I included some details from npm's handling that I cannot confirm is entirely replicated in other tools.