CLI tools behind a Nodejs namespace
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 694
- Forks
- 142
- PR merge metrics
- No merged PRs in 30d
Description
Not sure if this is the right place for this issue, so I am happy to move it. I opened it here because it affects multiple tools in the Node.js org.
Since the installation instructions on the Node.js tooling (ie. https://github.com/nodejs/node-core-utils, https://github.com/nodejs/changelog-maker, etc) recommend a global install, should these be put under a Node.js scope on the npm registry such as @nodejs/<packagename>?
It establishes a level of trust in the published packages ("I know this came from the Node org"), and it will hopefully help contributors avoid accidental installations of similarly named packages.
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
Review the installation instructions for node-core-utils, changelog-maker, and the other Node.js tooling named in the issue, then read the linked npm scope documentation. Determine which tools would need an @nodejs package scope and document the agreed package-publishing approach; done means the TSC has a clear decision for the affected tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100