Tee Ming

> Sorry for the naive question but the single worker basically is the server-side part of a regular sveltekit build, correct? Yes, that's right.

Hi @Lms24 I tried re-arranging the exports order for `@sentry/sveltekit` so that it discovers the worker export before the browser one. ```json "exports": { "./package.json": "./package.json", ".": { "types": "./build/types/index.types.d.ts",...

We're still bundling in the Cloudflare workers adapter until https://github.com/sveltejs/kit/pull/13072 is merged. Maybe we can separate that and the Workers Static Assets change into different PRs.

Please provide a minimal reproduction in the form of a repository with expected results and actual results. It's difficult to reproduce the issue from following instructions spread out through multiple...

> Given that we changed this in Svelte 5, I would rather not fix this within Svelte 4 (if it's a Svelte issue). Does one of the suggested workarounds in...

Closing this as it's fixed in Svelte 5

Are you facing this issue with `pnpm` specifically? https://github.com/volta-cli/volta/issues/1743#issuecomment-2096122673 might help. When I run `node -v` it shows me the version I switched to. But previously, running `pnpm node -v`...

It sounds like the same problem I had where the Node version I've set with Volta is not the same as what pnpm uses. Try adding this to your shell...

> > It sounds like the same problem I had where the Node version I've set with Volta is not the same as what pnpm uses. Try adding this to...