[RRFC] Deprecating the npx package from the public registry
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 777
- Forks
- 267
- PR merge metrics
- No merged PRs in 30d
Description
⚠️ [DISCLAIMER]: npx as a command now lives within the npm cli, it's not going anywhere and we love it - this discussion is only about deprecating the npx package published in the npm registry.
We know we want to deprecate the npx package but what exactly does that mean?
- Simply putting up a deprecation notice for the package in the registry?
- Cut a new major version and point it to install npm instead?
- Some other/diff ideas?
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 npx package listing in the public npm registry and the three deprecation options described in the issue. Establish which registry action or package release should be chosen, then document the agreed path and its expected effect on users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100