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
Make SvelteKit SDK use Vercel Edge runtime SDK #9107
Hey @isaacharrisholt - for sure. Sorry we gave you a false ok for the last time, we had to figure stuff out technically on our side. Now we are in a better place with the @sentry/vercel-edge package, so we can just add it to the SvelteKit SDK.
This is a little tricky because we use a multiplexer approach via a webpack plugin in nextjs so that the SDK automatically switches between using the edge or node sdk. @lforst any tips on the SvelteKit SDK?
Hacking this in is going to be hard. I suggest waiting for official support from our SDK. This is likely gonna happen near- to medium term.
Don't mean to nag, but what do near and medium term mean to you? We're likely going to have to move away from sentry due to the lack of edge support, but I want to make sure we don't do that if this is right around the corner.
Don't mean to nag, but what do near and medium term mean to you? We're likely going to have to move away from sentry due to the lack of edge support, but I want to make sure we don't do that if this is right around the corner.
@knd775 1 month to 3 or so? Sveltekit is one of our smaller SDKs and the intersection of Sveltekit SDK users and Vercel Edge users is even smaller. It does not make sense for us to put this at a higher priority.
PRs are always welcome. The building blocks should all be there since we now have the @sentry/vercel-edge package which you could probably even use in its current form. Note that it is in alpha and doesn't contain any docs yet.
Going to close this because realistically we won't get to this for the moment. Edge runtime doesn't seem to be recommended anymore so we'll rather focus on other runtimes.
Activity
isaacharrisholt commentedon Sep 25, 2023
Hey again! Is there any way I can contribute to this?
AbhiPrasad commentedon Sep 25, 2023
Hey @isaacharrisholt - for sure. Sorry we gave you a false ok for the last time, we had to figure stuff out technically on our side. Now we are in a better place with the
@sentry/vercel-edgepackage, so we can just add it to theSvelteKitSDK.This is a little tricky because we use a multiplexer approach via a webpack plugin in nextjs so that the SDK automatically switches between using the edge or node sdk. @lforst any tips on the SvelteKit SDK?
We can probably use a similar strategy to sveltekit adapter auto to decide between using
@sentry/nodeand@sentry/vercel-edgehttps://github.com/sveltejs/kit/tree/master/packages/adapter-auto if the multiplexer is too complex, maybe a good first step.lforst commentedon Sep 26, 2023
Hacking this in is going to be hard. I suggest waiting for official support from our SDK. This is likely gonna happen near- to medium term.
knd775 commentedon Oct 12, 2023
Don't mean to nag, but what do near and medium term mean to you? We're likely going to have to move away from sentry due to the lack of edge support, but I want to make sure we don't do that if this is right around the corner.
lforst commentedon Oct 13, 2023
@knd775 1 month to 3 or so? Sveltekit is one of our smaller SDKs and the intersection of Sveltekit SDK users and Vercel Edge users is even smaller. It does not make sense for us to put this at a higher priority.
PRs are always welcome. The building blocks should all be there since we now have the
@sentry/vercel-edgepackage which you could probably even use in its current form. Note that it is in alpha and doesn't contain any docs yet.68 remaining items
Lms24 commentedon Feb 11, 2026
Going to close this because realistically we won't get to this for the moment. Edge runtime doesn't seem to be recommended anymore so we'll rather focus on other runtimes.