[Feature] Global and project specific config to pin package version for npx
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
the default behavior of always fetching for latest version does more harm than good. We NEED a way to keep agentic tools/workflows stable and working when they all use npx xxx and xxx might be broken in a new update.
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 at the npx entry point and trace how it currently resolves and fetches package versions. Define how global and project-specific pins should interact with the default latest-version behavior; done means both scopes can keep npx-based tools stable without ambiguity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100