Sveltekit scope management?

[alexbjorlig]

When using the Sveltekit Sentry SDK, do we need to manage scope manually or will the out-of-the box configuration "just" work.

I.e, if I call:

import * as Sentry from '@sentry/sveltekit';

// in the handle function
Sentry.setTag('requestId', requestId);

Will the requestId be "scoped" for every single request, or does it pollute a more global scope? (so one request would be able to touch the scope from an other request?)

Thanks 🙏

[AbhiPrasad]

hey! For server-side everything will be scoped to a single request. For client-side there is no async context APIs we can use in the browser, so it will affect things globally.

[alexbjorlig]

Hi @AbhiPrasad - thanks for the quick reply 👍 I'm only thinking about the server in this context. Do you mind sharing some insights - and follow-up questions?

1. How does this work?
2. Are there some requirements for it to work, i.e. where Sentry must be installed?
3. Will it also work if deployed to edge functions - i.e. not-node runtimes?

We are currently deployed with Vercel using edge functions. Thank you so much 🙏

[AbhiPrasad]

1. Under the hood the SDK uses AsyncLocalStorage for async context isolation. You can see it described more detail in our docs. This is done automatically for you in SvelteKit Sentry SDK, no need to worry about setting it up.
2. Sentry must be installed via the SvelteKit SDK instructions in https://docs.sentry.io/platforms/javascript/guides/sveltekit/ for this to work
3. Currently the Sentry SvelteKit SDK only supports the Node.js runtime. We have a task for vercel edge runtime here: Make SvelteKit SDK use Vercel Edge runtime SDK #9107