nodejs / nodejs/package-maintenance
Take over `node-versions` package
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
This package gets 40M downloads a week and has not been seeing regular publishes. I asked the maintainer if they would be interested in maybe handing it off and it looks like they are. Anyone opposed to pulling this functionality into @pkgjs/nv or working with the @nodejs/build or @nodejs/releasers to see if publishing this right from the release workflows makes sense?
I think it would be really simple to pull it in as a nightly in nv which was discussed briefly in https://github.com/pkgjs/nv/issues/10. If folks are open to this I can start the work to do that. If not I do think that publishing updated metadata to the npm registry at release time is a great longer term solution to folks needing this data.
cc @chicoxyzzy
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 by reading node-releases#37 and pkgjs/nv#10, then compare the proposed nightly publication with publishing from Node.js release workflows. No files or tests are named; done requires an agreed ownership and publishing direction before implementation can be scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100