docs(js): Remove the Connect guide and redirect it to Node

[JPeer264]

IMPORTANT

When we merge this we redirect /connect to /node with a permanent redirect. That means if in the future we'll readd /connect we have to choose another name because connect has a permanent redirect. Everyone that has that in their browser cache has it in there forever.

DESCRIBE YOUR PR

closes SDK-1498

v11 removed the Connect instrumentation, so @sentry/node exports neither setupConnectErrorHandler nor connectIntegration, and every app the guide printed crashed with TypeError: Sentry.setupConnectErrorHandler is not a function before it listened.

Nothing Connect specific is left to document. A Connect app is still instrumented by the generic Node HTTP instrumentation, so the Node guide covers it, and the guide now redirects there.

• Delete the Connect guide, the Connect integration page and the eleven Connect only platform includes.
• Drop javascript.connect from the frontmatter and PlatformSection lists of 117 pages, and from the Logs and Metrics platform pickers.
• Drop Connect from the request handler row of the span op table, in the migration page and in its include.
• Drop connect from the frameworks list of ten v11 migration items, which scripts/validate-migration-items.mjs validates against the guide directory.
• Point the React Native RequestData link at the Node guide.
• Redirect /platforms/javascript/guides/connect/ and everything under it to the Node guide.

The v8 migration pages keep their connectIntegration mentions, since they record what v8 shipped.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've supplied a deadline.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
develop-docs	Ready	Preview	Sep 11, 2026 2:40pm UTC
sentry-docs	Ready	Preview	Sep 11, 2026 2:40pm UTC

[linear-code]

SDK-1498

[github-actions]

⚠️ Redirect Chain Issues Detected

This PR introduces or contains redirect chains that degrade SEO and add latency.

Redirect-to-Redirect Chains

These redirect destinations point to another redirect, creating multi-hop chains. Update the destination to point directly to the final URL:

Source	Current Destination	Should Be	File
/clients/node/integrations/connect/	/platforms/javascript/guides/connect/	/platforms/javascript/guides/node/	middleware.ts
/platforms/node/connect/	/platforms/javascript/guides/connect/	/platforms/javascript/guides/node/	middleware.ts

---

Each redirect hop loses ~15% of SEO link equity and adds latency for users.