Repository navigation
docs: point inspector debugging link at current Node.js guide - #2588
Merged
Merged
Conversation
nodejs.org/en/docs/guides/debugging-getting-started/ now 404s. Use the current learn/getting-started/debugging page in both READMEs. Co-authored-by: FirmamentalSpring <287222957+FirmaSpring@users.noreply.github.com>
Collaborator
|
This is AI slop, but a small tidy change. |
Collaborator
|
@FirmaSpring Could you resolve the conflict? |
Author
I can try it |
…s/fix-nodejs-debugging-link # Conflicts: # Readme_zh-CN.md
Author
|
Resolved the conflict in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The README debugging section links to the retired Node.js guide:
https://nodejs.org/en/docs/guides/debugging-getting-started/
A curl -L GET of that URL returns 404. The same dead URL is also used in
Readme_zh-CN.md.Solution
Point both READMEs at the current Node.js debugging guide, which returns 200:
https://nodejs.org/en/learn/getting-started/debugging
Verification