Skip to content

docs: add Next.js server-side error capture to marketing pages - #729

Merged
cursor[bot] merged 1 commit into
developfrom
cursor/nextjs-server-error-docs-7a43
Oct 2, 2026
Merged

cursor[bot] merged 1 commit into
developfrom
cursor/nextjs-server-error-docs-7a43

Conversation

@unjica

@unjica unjica commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Base branch: open feature and fix PRs against develop. Milestone releases promote develop → main — see docs/RELEASE.md.

Summary

This PR updates the marketing site to accurately reflect that Next.js error tracking now includes server-side error capture via instrumentation.ts, not just client-side errors.

Changes:

  1. /error-tracking/nextjs page:

    • Added "Server errors (optional)" section with instrumentation.ts setup
    • Updated page description, lede, and structured data to mention server error capture
    • Reuses verified snippets: nextEnvLocalServer and nextInstrumentation from @/lib/sdk-setup-snippets
    • Links to full /docs/nextjs for details
  2. /sentry-alternative page:

    • Updated "Supported SDKs" section to clarify Next.js captures both client-side and App Router server errors when configured

Verified against:

  • @telemetry-tracker/next v1.3.2 package source
  • /docs/nextjs page content (canonical source)
  • Shared SDK setup snippets in @/lib/sdk-setup-snippets.ts

All changes use existing verified code snippets to prevent drift between docs and acquisition pages.

How to test

pnpm lint && pnpm test && pnpm build

All tests, lint checks, and build passed successfully.

Manual verification after deployment:

Code review (Bugbot)

Paused: GitHub bugbot-review is currently a no-op. /review-bugbot is optional.

  • For notification, alert, billing, ingest, or auth changes: considered running /review-bugbot in Cursor (optional while the gate is paused)
  • If Bugbot comments appear anyway: addressed or replied (resolve thread + update .cursor/BUGBOT.md if a finding was a false positive)

N/A — documentation-only changes.

Checklist

  • Tests pass (pnpm test; use RUN_DB_INTEGRATION_TESTS=true + Postgres if API integration behavior changed)
  • Lint passes (pnpm lint)
  • Build succeeds (pnpm build)
  • CHANGELOG.md updated under [Unreleased] (if user-facing)
  • Documentation updated (if needed)
  • New code follows the existing style
  • No breaking changes (or called out clearly above)

CHANGELOG update not required — these are marketing/SEO copy changes to align with existing functionality (instrumentation.ts support shipped in v1.3.2 / platform v1.17.23).

Security / privacy

N/A — documentation-only changes. No auth, ingest, or data-handling changes.

Open in Web Open in Cursor 

- Update /error-tracking/nextjs to include server errors section
  - Add imports for nextEnvLocalServer and nextInstrumentation snippets
  - Add 'Server errors (optional)' section with instrumentation.ts setup
  - Update page description and lede to mention server error capture
  - Update howToJsonLd structured data to mention optional server setup
- Update /sentry-alternative to clarify Next.js supports both client and server errors
  - Modify SDK description to note App Router server errors when configured
- All changes use existing verified snippets from @/lib/sdk-setup-snippets
- Verified against @telemetry-tracker/next 1.3.2 package source
- Tests pass: pnpm test (all tests), pnpm lint, pnpm build

Co-authored-by: Sanja Malovic <unjica@users.noreply.github.com>
@cursor
cursor Bot merged commit 50917b4 into develop Oct 2, 2026
7 checks passed
@cursor
cursor Bot deleted the cursor/nextjs-server-error-docs-7a43 branch October 2, 2026 10:24
cursor Bot added a commit that referenced this pull request Oct 2, 2026
* fix(sdk): sanitize Script error. reporting in @telemetry-tracker/core 1.5.1

Stop fabricating SDK stacks for browser-sanitized Script errors, rate-limit
identical floods, and label them clearly in the dashboard error detail view.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix(sdk): use const for sanitized Script error dedupe store

Co-authored-by: Cursor <cursoragent@cursor.com>

* docs: add Next.js server-side error capture to marketing pages (#729)

- Update /error-tracking/nextjs to include server errors section
  - Add imports for nextEnvLocalServer and nextInstrumentation snippets
  - Add 'Server errors (optional)' section with instrumentation.ts setup
  - Update page description and lede to mention server error capture
  - Update howToJsonLd structured data to mention optional server setup
- Update /sentry-alternative to clarify Next.js supports both client and server errors
  - Modify SDK description to note App Router server errors when configured
- All changes use existing verified snippets from @/lib/sdk-setup-snippets
- Verified against @telemetry-tracker/next 1.3.2 package source
- Tests pass: pnpm test (all tests), pnpm lint, pnpm build

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Sanja Malovic <unjica@users.noreply.github.com>

---------

Co-authored-by: cursor[bot] <206951365+cursor[bot]@users.noreply.github.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Sanja Malovic <unjica@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants