| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
SvelteKit 3 builds all environments in one Vite build and invokes the adapter in a post buildApp hook, so the closeBundle upload never ran. Upload from a post buildApp hook as well, once an environment has been built. Source maps were also never deleted after upload, because the deletion check read build.sourcemap after our own plugin had already set it. Fixes #25096 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sorry, something went wrong.
|
bugbot run |
Sorry, something went wrong.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 424ee8f. Configure here.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
SvelteKit 3 builds all environments in a single Vite build and runs the adapter in a post buildApp hook. Our upload waited for a separate SSR build in closeBundle, which Kit 3 never does, so nothing was uploaded. We now also upload from a post buildApp hook, but only once an environment has been built. Kit 2 builds only after all buildApp hooks have run, so its closeBundle path still does the upload.
Source maps were also never deleted after upload, on Kit 2 or Kit 3. The deletion check read build.sourcemap after our own plugin had already set it.
The new sveltekit-3-sourcemaps e2e app builds against a mock Sentry server. It asserts that the upload happens, that every debug ID has a map, and that no maps are left in build/.
Fixes #25096