Skip to content

docs(guide): fix dead Node.js debugging link in debug guide#10761

Closed
sanjibani wants to merge 1 commit into
vitest-dev:mainfrom
sanjibani:fix/nodejs-debug-link-docs-v2
Closed

docs(guide): fix dead Node.js debugging link in debug guide#10761
sanjibani wants to merge 1 commit into
vitest-dev:mainfrom
sanjibani:fix/nodejs-debug-link-docs-v2

Conversation

@sanjibani

Copy link
Copy Markdown

Summary

Fixes a dead external link in the debug guide.

  • docs/guide/debugging.md:133: https://nodejs.org/en/docs/guides/debugging-getting-started/ (HTTP 404) replaced with the canonical https://nodejs.org/en/learn/getting-started/debugging (200). nodejs.org retired the /en/docs/guides/ subpath in favor of /en/learn/.

Single-line change, single file. Verified the replacement returns 200.

docs/guide/debugging.md:133 points at https://nodejs.org/en/docs/guides/debugging-getting-started/ (HTTP 404; nodejs.org retired the /en/docs/guides/ subpath in favor of /en/learn/). Replaced with the canonical https://nodejs.org/en/learn/getting-started/debugging (200).

Verified the replacement target returns 200 and preserves the 'getting started with debugging' anchor intent of the original.
@github-actions github-actions Bot added the maybe automated User is likely an AI agent, or the content was generated by an AI assistant without user control label Jul 12, 2026
@github-actions

Copy link
Copy Markdown

Hello @sanjibani. Your PR has been labeled maybe automated because it appears to have been fully generated by AI with no human involvement.

To keep your PR open, please follow these steps:

  • Confirm that you are a real human. If you are an automated agent, disclose that
  • Confirm you've read, reviewed and stand behind its content
  • Confirm you've read the full issue along with all of its comments, as well as any linked issues and their comments
  • Make sure it follows our contribution guidelines and uses the correct GitHub template
  • Disclose any AI tools you used (e.g. Claude, Copilot, Codex)

Please, do not generate or format the response with AI. If you do not speak English, reply in your native language or use translation software like Google Translate or Deepl. If the response is generated, the PR will be closed automatically.

These measures help us reduce maintenance burden and keep the team's work efficient. See our AI contributions policy for more context.

@netlify

netlify Bot commented Jul 12, 2026

Copy link
Copy Markdown

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 5812299
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6a53b919225c7b000808ba28
😎 Deploy Preview https://deploy-preview-10761--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@sanjibani

Copy link
Copy Markdown
Author

hey maintainers — quick disclosure per the AI contributions policy.

I am a real person (sanjibani). I used an AI coding assistant (Claude via mavis) to help find the broken link and verify the replacement. The verification (HEAD + GET probes), the choice of replacement URL, and the final review were done by me. I've read the existing debug guide context and the related Vitest docs and stand behind the change.

happy to revise or close if the team prefers a different replacement. thanks for the work on vitest.

@github-actions github-actions Bot closed this Jul 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maybe automated User is likely an AI agent, or the content was generated by an AI assistant without user control

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant