@nx/js:node executor hangs while "watch": false option is set
Current Behavior
Run node app serve:production target with "watch": false option set hangs at the end and shows To exit the process, press Ctrl+C before the output.
Expected Behavior
Shouldn't the process exit after execution?
GitHub Repo
No response
Steps to Reproduce
- npx create-nx-workspace@latest test --preset=node-standalone --framework=none --docker=false --useGitHub=false --nxCloud=skip
- cd test
- add
"watch": falseto the/project.jsonfile at thetargets.serve.configurations.productionsection - run
npx nx run test:serve:production
Nx Report
Node : 20.15.1
OS : darwin-arm64
Native Target : aarch64-macos
npm : 10.7.0
nx : 19.6.2
@nx/js : 19.6.2
@nx/jest : 19.6.2
@nx/linter : 19.6.2
@nx/eslint : 19.6.2
@nx/workspace : 19.6.2
@nx/devkit : 19.6.2
@nx/esbuild : 19.6.2
@nx/eslint-plugin : 19.6.2
@nx/node : 19.6.2
@nrwl/tao : 19.6.2
typescript : 5.5.4
---------------------------------------
Registered Plugins:
@nx/eslint/plugin
@nx/jest/plugin
Failure Logs
No response
Package Manager Version
No response
Operating System
- [X] macOS
- [ ] Linux
- [ ] Windows
- [ ] Other (Please specify)
Additional Information
No response
We are running into the exact same problem. The watch: false flag also isn't being respected when we run a node executor via CLI.
Any idea when this might be fixed? We've not been able to update since this was introduced.
We have the same issue with the latest NX version (19.6.5)
Any plans to fix this? We're falling quite far behind latest now.
Still stuck on Nx version 19.5.7 here. Has anybody managed to work around this?
This issue has been automatically marked as stale because it hasn't had any activity for 6 months. Many things may have changed within this time. The issue may have already been fixed or it may not be relevant anymore. If at this point, this is still an issue, please respond with updated information. It will be closed in 21 days if no further activity occurs. Thanks for being a part of the Nx community! 🙏
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.