Release: Next.js server error documentation to production - #730
Merged
Merged
Conversation
….25-f4fb chore: sync main into develop after v1.17.25
… 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>
Co-authored-by: Cursor <cursoragent@cursor.com>
…rror-1.5.1 fix(sdk): @telemetry-tracker/core 1.5.1 sanitized Script error. handling
- 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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Base branch: promoting to
mainfor production deployment.Summary
Deploy the Next.js server-side error capture documentation updates to production (telemetry-tracker.com).
Merged to
develop: PR #729Changes:
/error-tracking/nextjsnow includes "Server errors (optional)" section/sentry-alternativeclarifies Next.js captures both client and server errorsThis is a documentation-only change to align marketing pages with the existing
@telemetry-tracker/next@1.3.2functionality (instrumentation.ts support).Deploy notes
mainwhen mergedChecklist
pnpm test)pnpm lint)pnpm build)developPost-deploy verification
After Railway deployment completes: