We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v22.0.0
Darwin 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 arm64
No response
Running a file with node --watch --inspect index.js will not start the inspector.
node --watch --inspect index.js
Order of flags --watch --inpect should not matter (like in node v21.x)
Inspector not starting on port :9229
When changing the order of flags from node --watch --inspect to node --inspect --watch the inspector starts on port :9229 like expected.
node --watch --inspect
node --inspect --watch
The text was updated successfully, but these errors were encountered:
@MoLow
Sorry, something went wrong.
I Will try taking a look next week. might be related to the changes in #52358
Successfully merging a pull request may close this issue.
Version
v22.0.0
Platform
Darwin 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000 arm64
Subsystem
No response
What steps will reproduce the bug?
Running a file with
node --watch --inspect index.js
will not start the inspector.How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
Order of flags --watch --inpect should not matter (like in node v21.x)
What do you see instead?
Inspector not starting on port :9229
Additional information
When changing the order of flags from
node --watch --inspect
tonode --inspect --watch
the inspector starts on port :9229 like expected.The text was updated successfully, but these errors were encountered: