Use executable shim launchers for binaries/scripts provided by packages instead of batch/powershell scripts
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
On Windows, the batch scripts used to launch installed binaries/scripts from packages result in the annoying "Terminate batch job [Y/N]" prompt whenever you hit Ctrl-C on one. Due to this, other scripts languages like Python, and Windows package mangers like scoop choose to instead generate shim launcher executables for such installed scripts so as to avoid this issue, and others related to PATHEXT priorities and so on.
It would be nice if npm implements this as well (And probably the other package managers pnpm, yarn might follow suit if it does).
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
No files, tests, or entry points are identified in the issue. First clarify which npm installation paths and Windows launcher behaviors are in scope, then define acceptance tests for Ctrl-C, PATHEXT, and package-provided binaries or scripts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100