not yet anyway. But will be in a few months

--- @rp_st Just personal thoughts: I get really nervous when I see the SuperTokens team providing "solutions" requiring React for other frontend frameworks. This forces developers to bring a much larger bundle size than should be necessary to their applications. And my assumption is that many devs will not buy this hack (because they're intentionally leaving React for Vue/Svelte/Solid/etc. to avoid bloat and performance issues). When I first saw it with Vue, I assumed it was a one-off thing. But now that this seems to be a thing with Svelte, I really think the ST team should reconsider their approach. We want to attract users and support more devs, yes. But no dev wants to download several React packages to get a Svelte/Vue app up and running. I think a better solution would be for the team to take time to consider what each individual framework needs, and to build solutions around that framework (instead of trying to shoehorn React in). If the team doesn't have time for this, it might be worth hiring a frontend dev who has this knowledge, or giving more support to devs in the community who have this knowledge. It's also possible that refactors in more central libraries could be useful (just like how refactors in

supertokens-node

made SvelteKit support easier). It also might be worthwhile for the ST Team to review the SvelteKit repo that I made (and potentially make updates). When I suggested it earlier, it seems the team didn't have time to look into it. But looking into that project (which has been around for awhile) might prove easier than trying to write examples like the one you linked. And it may result in something more aligned with what Svelte devs truly want.

I’m terms of maintaining the sveltekit app, we really don’t have time for it even now (unfortunately). We have a 2 big features (MFA and Oauth provider) that we need to build, and then perhaps after that we can take over the sveltekit repo :). That being said, thank you for making it