Skip to content

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

Closed
sanjibani wants to merge 2 commits into
vitest-dev:mainfrom
sanjibani:fix/nodejs-debug-link-docs
Closed

docs(guide): fix dead Node.js debugging link in debug guide#10760
sanjibani wants to merge 2 commits into
vitest-dev:mainfrom
sanjibani:fix/nodejs-debug-link-docs

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.

- SECURITY.md:5: 'https://vitest.dev/releases' returns 404. The releases
  page lives on GitHub at 'https://github.com/vitest-dev/vitest/releases'
  (HTTP 200, same content).
- docs/blog/vitest-3.md:34: 'https://storybook.js.org/docs/writing-tests/test-addon'
  returns 404 (the path was restructured when the Vitest addon was
  promoted to a first-class integration). The new canonical path is
  'https://storybook.js.org/docs/writing-tests/integrations/vitest-addon'
  (HTTP 200, same content: vscode extension + browser mode).

No content text changes.
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.

@sanjibani sanjibani closed this Jul 12, 2026
@sanjibani
sanjibani deleted the fix/nodejs-debug-link-docs branch July 12, 2026 15:55
@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 135da25
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6a53b8eb33eed5000828475d
😎 Deploy Preview https://deploy-preview-10760--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.

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