-
-
Notifications
You must be signed in to change notification settings - Fork 34.7k
Open
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.watch-modeIssues and PRs related to watch modeIssues and PRs related to watch mode
Description
Version
v25.6.0
Platform
Darwin <redacted> 24.6.0 Darwin Kernel Version 24.6.0: Wed Nov 5 21:33:58 PST 2025; root:xnu-11417.140.69.705.2~1/RELEASE_ARM64_T6000 arm64 arm Darwin
Subsystem
No response
What steps will reproduce the bug?
- Write the following to
test.jsand make it executable:#!/usr/bin/env node console.log('hello');
NODE_OPTIONS="--watch" ./test.js
How often does it reproduce? Is there a required condition?
This is always reproducible.
What is the expected behavior? Why is that the expected behavior?
I would expect it to run normally, producing hello in stdout and then exiting.
What do you see instead?
There is no output. I can see in my process list that there are hundreds of node processes spawning.
Additional information
This seems to be the same issue as #51159. For additional context, my intent was to reuse a bin entrypoint in package.json but with --watch mode, so under the scripts field it looked roughly like:
"scripts": {
"dev": "NODE_OPTIONS='--watch' app",
}...where app is in node_modules/.bin/.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.watch-modeIssues and PRs related to watch modeIssues and PRs related to watch mode