You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
It looks like the new version of Svelte is incompatible with the @sentry/sveltekit package. Removing the latter allows for successful compilation. #16507
I've got a similar issue with Sentry SDK 9.27, latest macOS.
SvelteKit 2.21.2 compiles correctly.
SvelteKit 2.21.3 produces the following error:
✗ Build failed in 2.88s
error during build:
[commonjs--resolver] node_modules/.pnpm/fsevents@2.3.3/node_modules/fsevents/fsevents.node (1:0): Unexpected character '�' (Note that you need plugins to import files that are not JavaScript)
file: /Users/dmitrii/work/repunzel/app/node_modules/.pnpm/fsevents@2.3.3/node_modules/fsevents/fsevents.node:1:0 (/Users/dmitrii/work/repunzel/app/node_modules/.pnpm/@sentry+sveltekit@9.27.0_@opentelemetry+api@1.9.0_@opentelemetry+context-async-hooks@1._9444b30d78254d4fbc240375a95ddf1d/node_modules/@sentry/sveltekit/build/cjs/index.server.js)
1: ����@<�
��*...
^
4*
h���/System/Library/Frameworks/CoreFoundation.framework/Versions...
3: ���H��1�H���L���L���H�����L�E�L��H��1�����uH�E�H�[A^A_]��}f.�UH��AWAVSPI��H��I��H�H...
at getRollupError (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/parseAst.js:401:41)
at ParseError.initialise (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/node-entry.js:14293:28)
at convertNode (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/node-entry.js:16197:10)
at convertProgram (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/node-entry.js:15440:12)
at Module.setSource (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/node-entry.js:17185:24)
at async ModuleLoader.addModuleSource (file:///Users/dmitrii/work/repunzel/app/node_modules/.pnpm/rollup@4.41.2/node_modules/rollup/dist/es/shared/node-entry.js:21187:13)
ELIFECYCLE Command failed with exit code 1.
Hey, just leaving an update here as well: It looks like there were some bundling changes made in the latest Kit version which don't play well with our package. I did some investigation in #16528 which doesn't yet fix fixes the problem but I need some input from the Svelte team as well on this. Sorry for the inconvenience!
Update: We figured out the remaining piece of the puzzle. This should be fixed by EOD.
Activity
snide commentedon Jun 9, 2025
Small comment that I ran into this as well this morning when updating my weekly dependencies.
gregg-cbs commentedon Jun 9, 2025
I am now getting:
"The requested module '@sentry/core' does not provide an export named 'default'" when building but dev runs fine.
Build is happening in docker so i think there some version mismatch happening somewhere. It should not be happening.
fuwaneko commentedon Jun 9, 2025
I've got a similar issue with Sentry SDK 9.27, latest macOS.
SvelteKit 2.21.2 compiles correctly.
SvelteKit 2.21.3 produces the following error:
sopaco commentedon Jun 10, 2025
According to the initial assessment of the Svelte community, this is a bug in the new version of the kit.
sveltejs/kit#13869
test(sveltekit): Pin `@sveltejs/kit@2.21.2` to unblock CI (#16529)
Lms24 commentedon Jun 11, 2025
Hey, just leaving an update here as well: It looks like there were some bundling changes made in the latest Kit version which don't play well with our package. I did some investigation in #16528 which
doesn't yet fixfixes the problembut I need some input from the Svelte team as well on this. Sorry for the inconvenience!Update: We figured out the remaining piece of the puzzle. This should be fixed by EOD.
Lms24 commentedon Jun 11, 2025
closing as completed via #16528. Once this is released, you'll get another notification in this issue
github-actions commentedon Jun 11, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #16528, which was included in the 9.28.1 release.