[BUG] IOT instruction (core dumped) on `npx --node-options='--watch'`
Open
Nobody has claimed this yet.
Bug
Needs Triage
Release 8.x
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
Running npx with --node-options='--watch' results in core dumped.
Expected Behavior
Running npx with --node-options='--watch' should run with the specified node options passed to node.
Steps To Reproduce
Run npx --node-options='--watch' debris
Environment
- npm: 8.19.2
- Node.js: v20.2.0
- OS Name: Arch Linux
- System Model Name: Thinkpad X1 gen 6
- npm config:
; copy and paste output from `npm config ls` here
; "user" config from /home/blue/.npmrc
//registry.npmjs.org/:_authToken = (protected)
; node bin location = /usr/bin/node
; node version = v20.2.0
; npm local prefix = /home/blue/app
; npm version = 8.19.2
; cwd = /home/blue/app
; HOME = /home/blue
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 reproducing the failure with npx --node-options='--watch' debris in the reported npm 8.19.2 and Node.js v20.2.0 environment. Trace the npx handling of --node-options and compare it with a normal invocation. Done means the command runs without dumping core and passes the specified Node options to Node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100