feat(javascript): Add interactive JavaScript v11 migration guide - #19076
Draft
msonnb wants to merge 2 commits into
Draft
feat(javascript): Add interactive JavaScript v11 migration guide#19076msonnb wants to merge 2 commits into
msonnb wants to merge 2 commits into
Conversation
Adds an interactive guide for the Sentry JavaScript SDK v10-to-v11 upgrade, rendered into every JavaScript platform and guide page via `<MigrationGuide />`. - 88 breaking changes as standalone MDX items in `includes/migration/javascript-v11/`, each tagged with the phase, severity, frameworks, platform category and features it applies to - A server component that drops items the current guide cannot use, and a client shell owning facet filtering, per-guide checklist state and the copy-for-agent prompt - Setup detection that reads facets and the SDK package off a pasted `package.json` or `Sentry.init()` block, and links readers to the right guide when they are on the wrong one - A frontmatter validator run by `pnpm test`, with `pnpm migration-items` for the breakdown by phase, severity and category - Interactive chrome is excluded from the `.md` exports, so agents fetching a page get the guide without controls they cannot operate Adds the missing `categories` frontmatter to the Effect guide, without which the migration page showed browser-only items on a server-only SDK. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Note
This is a hackweek project
DESCRIBE YOUR PR
Adds an interactive guide for the Sentry JavaScript SDK v10-to-v11 upgrade, rendered into every JavaScript platform and guide page via
<MigrationGuide />.includes/migration/javascript-v11/, each tagged with the phase, severity, frameworks, platform category and features it applies topackage.jsonorSentry.init()block, and links readers to the right guide when they are on the wrong onepnpm test, withpnpm migration-itemsfor the breakdown by phase, severity and categoryAdds the missing
categoriesfrontmatter to the Effect guide, without which the migration page showed browser-only items on a server-only SDK.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: