Svelte 5 support

[ieedan]

Currently trying to use this in Svelte 5 doesn't work because of the following error:

Error: Your application, or one of it's dependencies, imported from 'svelte/internal', which was a private module used by Svelte 4 components that no longer exists in Svelte 5.

Since this package is fairly new I can't imagine a whole lot of Svelte 4 users are using it yet so it seems fine to introduce a breaking change to support Svelte 5 instead.

Also updated the svelte-example and usage on the site.

Fixes #18

[vercel]

@ieedan is attempting to deploy a commit to the Lochie's projects Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
torph	Ready	Preview, Comment	Feb 22, 2026 10:38pm
torph-svelte-example	Ready	Preview, Comment	Feb 22, 2026 10:38pm
torph-vue-example	Ready	Preview, Comment	Feb 22, 2026 10:38pm

[ieedan]

Fixed the props!

[ieedan]

My bad forgot to bump vite along with it. Also removed some unnecessary config from the vite.config since we are using the workspace protocol we don't need that.

[lochie]

@ieedan is this building locally for you? im seeing this error

Caution

error during build:
[vite]: Rollup failed to resolve import "torph/svelte" from "/vercel/path0/apps/svelte-example/src/App.svelte".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external

[ieedan]

Yeah it was building locally

[ieedan]

Okay was able to reproduce in my own Vercel deployment I guess that vite config is necessary after all. Weird I have never run into that before.

In any case it should work now!

[jaydenfyi]

I assumed Svelte 4 was an intentional choice for backwards compatibility, given Svelte 5 can use Svelte 4 components, but not vice-versa. Was that not the case @lochie ?

EDIT: Apologies I skipped past the PR description here 😅 Agree I don't think it really matters all things considered, most libraries are starting to cut over to 5 now.

I'm happy to look into it tomorrow if backwards-compatibility is desired. I'm assuming it's just some weird compilation issue with tsup causing Svelte code being compiled somewhere it shouldn't be.

[lochie]

I'm happy to look into it tomorrow if backwards-compatibility is desired. I'm assuming it's just some weird compilation issue with tsup causing Svelte code being compiled somewhere it shouldn't be.

@jaydenfyi i dont personally use svelte so im not aware of the desires of the ecosystem. im happy to roll with whatever you two unanimously are happy with!

[lochie]

@ieedan this PR looks good to me. but keen to understand the ideal scenario here re: 4 <> 5 support

[ieedan]

Svelte 4 should provide cross compatibility but the reason I raised this PR is that unfortunately at this time does not and Svelte 5 is broken.

Since you can technically use Svelte 4 and 5 together in the same app I don't see any reason to support Svelte 4 at the expense of Svelte 5. Consumers can simply update their Svelte version at any time to use this library.