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

src, lib: deprecate old debug-agent and CLI debugger #10276

Closed
wants to merge 2 commits into from

Conversation

joshgav
Copy link
Contributor

@joshgav joshgav commented Dec 15, 2016

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

src, debugger

Description of change

Per #9789 the old V8 debugger and its protocol are on their way out 👋 .

This prints a deprecation warning to stderr when node is invoked with --debug or debug. --debug starts the debug-agent within the process; debug starts Node's builtin CLI debugger. Both utilize the old V8 debugger protocol.

V8 inspector and --inspect replace --debug. Work is underway to replace the CLI debugger (i.e. node debug), see #10187.

I didn't use util.deprecate on the _debugger.start() function because it would print within the repl, i.e. prefixed with debug> .

/cc @nodejs/diagnostics

Print a warning if --debug or debug are used on the command line.

PR-URL: <tbd>
Reviewed-By: <tbd>
Reviewed-By: <tbd>
@joshgav joshgav added debugger lib / src Issues and PRs related to general changes in the lib or src directory. notable-change PRs with changes that should be highlighted in changelogs. inspector Issues and PRs related to the V8 inspector protocol labels Dec 15, 2016
@nodejs-github-bot nodejs-github-bot added c++ Issues and PRs that require attention from people who are familiar with C++. debugger labels Dec 15, 2016
@jkrems
Copy link
Contributor

jkrems commented Dec 16, 2016

Do we want to just pull in the soft deprecation (doc update) into this PR as well or is that taken care of in another place?

@Trott
Copy link
Member

Trott commented Dec 17, 2016

Do we want to just pull in the soft deprecation (doc update) into this PR as well or is that taken care of in another place?

I'd be inclined to put that in as a separate PR so that it doesn't get held up in case there are issues with a runtime deprecation. Is anyone stepping up to do the doc deprecation? I guess it would just be a note in doc/api/debugger.md?

@jkrems jkrems mentioned this pull request Dec 17, 2016
2 tasks
@jkrems
Copy link
Contributor

jkrems commented Dec 17, 2016

Since I couldn't find a PR that does it yet: #10320

@@ -27,6 +27,7 @@ exports.start = function(argv, stdin, stdout) {
stdout = stdout || process.stdout;

const args = [`--debug-brk=${exports.port}`].concat(argv);
console.error('`node debug` is deprecated, use `node inspect` instead.\n');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If possible, this should be updated to use process.emitWarning() and DeprecationWarning instead.

@jasnell jasnell added the semver-major PRs that contain breaking changes and should be released in the next major version. label Dec 23, 2016
@joshgav
Copy link
Contributor Author

joshgav commented Jan 23, 2017

closed in favor of #10970 for node --debug and #10187 for node debug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ Issues and PRs that require attention from people who are familiar with C++. inspector Issues and PRs related to the V8 inspector protocol lib / src Issues and PRs related to general changes in the lib or src directory. notable-change PRs with changes that should be highlighted in changelogs. semver-major PRs that contain breaking changes and should be released in the next major version.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants