Skip to content
New issue

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

node --inspect-brk --debug prints incorrect error message #28588

Closed
fasttime opened this issue Jul 7, 2019 · 0 comments · Fixed by #28589
Closed

node --inspect-brk --debug prints incorrect error message #28588

fasttime opened this issue Jul 7, 2019 · 0 comments · Fixed by #28589

Comments

@fasttime
Copy link
Contributor

fasttime commented Jul 7, 2019

  • Version: 12.6.0
  • Platform: Darwin 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64
$ node --inspect-brk --debug
node: [DEP0062]: `node --inspect --debug-brk` is deprecated. Please use `node --inspect-brk` instead.

Two issues here. The error message suggests that node was called with options --inspect and --debug-brk which is not the case. And it recommends using --inspect-brk instead, one of the options actually used.

cjihrig added a commit to cjihrig/node that referenced this issue Jul 9, 2019
This commit simplifies the DEP0062 error logic. Instead of
looking for certain combinations of flags, just show an error
for any usage of --debug or --debug-brk.

PR-URL: nodejs#28589
Fixes: nodejs#28588
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
targos pushed a commit that referenced this issue Jul 20, 2019
This commit simplifies the DEP0062 error logic. Instead of
looking for certain combinations of flags, just show an error
for any usage of --debug or --debug-brk.

PR-URL: #28589
Fixes: #28588
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: Franziska Hinkelmann <[email protected]>
Reviewed-By: Rich Trott <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant