Skip to content

docs(js): Remove the lightweight mode page, document openTelemetryIntegration - #19516

Draft
JPeer264 wants to merge 1 commit into
masterfrom
janpeer/sdk-1352-prepare-pr-to-remove-lightweight-mode-page
Draft

JPeer264 wants to merge 1 commit into
masterfrom
janpeer/sdk-1352-prepare-pr-to-remove-lightweight-mode-page

Conversation

@JPeer264

Copy link
Copy Markdown
Member

DESCRIBE YOUR PR

closes SDK-1352

v11 has no lightweight mode. @sentry/node-core was merged back into @sentry/node, so @sentry/node-core/light no longer exists and the whole page described a setup that cannot be followed.

The OTLP half of that page survives in a different form. The integration moved to the main export of every server SDK and was renamed to openTelemetryIntegration(), because it sends nothing over OTLP. Give it its own integration page covering what it does, the exporter wiring through getOtlpTracesEndpoint(), and the enableOpenTelemetrySetup caveat for @sentry/nextjs and @sentry/sveltekit.

The removed setupOtlpTracesExporter and collectorUrl options are not carried over: you configure the exporter yourself now.

  • Drop the lightweight entry from the installation methods page.
  • Point the "simpler way to bridge your existing setup" line on the custom OpenTelemetry setup page at the new integration.
  • Point the Node.js card on the OTLP concepts page there too.
  • Redirect /install/lightweight/ to the new page for the seven guides that served it.

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

…egration

v11 has no lightweight mode. `@sentry/node-core` was merged back into
`@sentry/node`, so `@sentry/node-core/light` no longer exists and the
whole page described a setup that cannot be followed.

The OTLP half of that page survives in a different form. The integration
moved to the main export of every server SDK and was renamed to
`openTelemetryIntegration()`, because it sends nothing over OTLP. Give it
its own integration page covering what it does, the exporter wiring
through `getOtlpTracesEndpoint()`, and the `enableOpenTelemetrySetup`
caveat for `@sentry/nextjs` and `@sentry/sveltekit`.

The removed `setupOtlpTracesExporter` and `collectorUrl` options are not
carried over: you configure the exporter yourself now.

- Drop the lightweight entry from the installation methods page.
- Point the "simpler way to bridge your existing setup" line on the
  custom OpenTelemetry setup page at the new integration.
- Point the Node.js card on the OTLP concepts page there too.
- Redirect `/install/lightweight/` to the new page for the seven guides
  that served it.

Refs SDK-1352
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@JPeer264 JPeer264 self-assigned this Sep 18, 2026
@vercel

vercel Bot commented Sep 18, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
develop-docs Ready Ready Preview Sep 19, 2026 3:41pm UTC
sentry-docs Ready Ready Preview Sep 19, 2026 3:41pm UTC

Request Review

@JPeer264
JPeer264 added this pull request to stack #19517 September 18, 2026 12:03
@linear-code

linear-code Bot commented Sep 18, 2026

Copy link
Copy Markdown

SDK-1352

@github-actions github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Sep 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Redirect Chain Issues Detected

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

Content Links Pointing to Redirects (1 found)

These links point to URLs that redirect. Update them to point directly to the final destination:

File Line Current Link Should Be
includes/docs-changelog.mdx 121 /platforms/javascript/guides/node/install/lightweight/ /platforms/javascript/guides/node/configuration/integrations/opentelemetry/

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

@JPeer264
JPeer264 force-pushed the janpeer/sdk-1352-prepare-pr-to-remove-lightweight-mode-page branch from 4160d45 to 907549f Compare September 19, 2026 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

js-v11-docs Priority: Needs Triage The PR description is missing valid priority information

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant