Conversation
`sentrySvelteKit` no longer lives on the `@sentry/sveltekit` entry, so every snippet that imported it from there fails the build with `SyntaxError: The requested module '@sentry/sveltekit/build/esm/index.server.js' does not provide an export named 'sentrySvelteKit'`. The plugin is exported only from `@sentry/sveltekit/vite`. Update all thirteen snippets on the current pages: - the three `vite.config` snippets in the getting-started include - the four in the source maps overview - the three in the source maps primer - the three on the build configuration page Also update the primer for the removed `sourceMapsUploadOptions`: its fields sit at the top level of the plugin options now, which the snippet already showed but the prose did not, and `url` became `sentryUrl`. The v8 and v10.7.0 manual setup pages keep the old import, since it was correct on those versions, and the migration entries keep it as their "Before" example. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
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.
DESCRIBE YOUR PR
closes SDK-1485
sentrySvelteKitno longer lives on the@sentry/sveltekitentry, so every snippet that imported it from there fails the build withSyntaxError: The requested module '@sentry/sveltekit/build/esm/index.server.js' does not provide an export named 'sentrySvelteKit'. The plugin is exported only from@sentry/sveltekit/vite.Update all thirteen snippets on the current pages:
vite.configsnippets in the getting-started includeAlso update the primer for the removed
sourceMapsUploadOptions: its fields sit at the top level of the plugin options now, which the snippet already showed but the prose did not, andurlbecamesentryUrl.The v8 and v10.7.0 manual setup pages keep the old import, since it was correct on those versions, and the migration entries keep it as their "Before" example.
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-DDwith the due date. You can update this information later by editing the PR description.SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
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