Native support for Svelte

[pensierinmusica]

Summary

Native support for Svelte

Motivation

The Svelte JS front-end framework is becoming popular and there are many request to have native support for it in Sentry

Additional Context

https://forum.sentry.io/t/requesting-svelte-support/8477

And until the native integration is live, what is your suggested way to load or lazy load Sentry in Svelte?

[chadwhitacre]

Thanks @pensierinmusica, routing to @getsentry/team-webplatform for triage [internal].

[HazAT]

Hey @pensierinmusica Svelte SDK is on our plan for Q1 2021
Keep an eye for updates, I've already commented a while back how it should run using Sentry now
sveltejs/svelte#1096 (comment)

[olivierchatry]

Hello !
Any update on this task ?

[rhcarvalho]

@olivierchatry, we were stretched too thin and were not able to ship this Q1 as planned as we've been busy working on other features like the Next.js SDK.

The current plan is to work on this in the second semester, but, as always, we're open to review PRs if someone in the community gets to this before us.

[olivierchatry]

That's is really not great news. We are switching from Ember to Svelte, and so our subscription to Sentry is basically useless now. It's OK, I will try to find another solution.

Thanks for the reply.

[ChrisOgden]

@olivierchatry I am working on a project that has sentry for svelte. It may not be a fully flushed out solution but would be happy to share some samples. The svelte discord is also very active with high chance others are doing similar. I agree it is disappointing this got pushed. Feel free to reach out to discuss with me.

[rhcarvalho]

Reminder that the existing SDK for Browser should work fine with Svelte too, even before we make something special for Svelte like we've been building for Next.js.

sveltejs/svelte#1096 (comment)

[rhcarvalho]

Input on what could be better in terms of user experience with @sentry/browser + Svelte would be highly appreciated.

[olivierchatry]

I'm going to try with @sentry/browser , as I would really like to continue with sentry. I don't think I need the fancy component boundaries, as for me the callstack + crash would be good enough. Thanks !

…

On Mon, May 3, 2021 at 8:28 PM Rodolfo Carvalho ***@***.***> wrote: Input on what could be better in terms of user experience with @sentry/browser + Svelte would be highly appreciated. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3494 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVOG7BSWHQQ5U53K267ETTL3TLHANCNFSM44BFR4ZQ> .

[olivierchatry]

@rhcarvalho works really well.

[smeubank]

To continue this discussion I'd like to share some of the internal conversation the team has been having around Svelte

1. @sentry/browser really good OOTB for Svelte - we provide some docs
2. create a wrapper around @sentry/browser following existing @sentry/framework pattern

• if svelte does need anything special in the future users wouldn't need to update and browser would still work OOTB as is

3. if there is something which requires special consideration in Svelte today it is

• perf monitoring and routing instrumentation (parameterization for useful routes )
• support for sveltekit
• these could both be out of the initial scope however

Would be great to get folks thoughts, experience, or support for working towards something like this!

@AbhiPrasad and @HazAT 👏 for the input

[shrink]

@smeubank I think it's worth considering SvelteKit as an important part of the integration, rather than as out of scope. SvelteKit has a great deal of activity at the moment and is a major part of the future of Svelte. My speculation (as a user of Svelte with zero involvement in the project itself) is that SvelteKit will become the dominant way to use Svelte over the long term because the broader frontend ecosystem is moving towards some server-side rendering (next.js being the leader in the space at the moment).

[smeubank]

thanks @shrink !

We don't have any strict plan/road map at the moment. But thinking out loud (read typing). Maybe a good route then would be option 1 with the wrapper and if we want to do something dedicated with svelte kit

1. wrapper style support would cover folks just wanting to build SPA
2. SvelteKit is [still in beta](https://kit.svelte.dev/docs/introduction) if I understand well

• and support for this could be stage 2 for folks who want to build with SvelteKit more similar to NextJs - want backend API and SSR type support

[AbhiPrasad]

Hey folks, we've started looking at working on @sentry/svelte. If there's something you'd like to see, please let us know! #5492