{ "stagedVersions": { "whatever": "other", "metadata": "we wanna", "put": "here", "versions": { "1.2.3": { "manifest": "data..." }, "1.2.4": { "another": "staged manifest..." } } } }The registry will support a data structure like this:
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 778
- Forks
- 266
- PR merge metrics
- No merged PRs in 30d
Description
The registry will support a data structure like this:
{
"stagedVersions": {
"whatever": "other",
"metadata": "we wanna",
"put": "here",
"versions": {
"1.2.3": { "manifest": "data..." },
"1.2.4": { "another": "staged manifest..." }
}
}
}
Discussion still to be had about what the dist field ought to look like in staged version manifests.
Originally posted by @isaacs in https://github.com/npm/rfcs/issues/92#issuecomment-586133495
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the stagedVersions JSON structure in this issue and review the discussion linked from RFC #92. Clarify and document the agreed shape of the dist field in staged version manifests; the issue names no implementation files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100