uncaught error import svelte/internal

[Konfekt]

Just wondering about the severity of

Uncaught Error: Your application, or one of its dependencies, imported from 'svelte/internal', which was a private module used by Svelte 4 components that no longer exists in Svelte 5. It is not intended to be public API. If you're a library author and you used 'svelte/internal' deliberately, please raise an issue on https://github.com/sveltejs/svelte/issues detailing your use case.

in

svelte/packages/svelte/src/motion/tweened.js

Line 10 in 7ce2dfc

import { get, render_effect } from 'svelte/internal/client';

as this is thrown in other packages robinscholz/svelte-inline-svg#48 as well. Must it be fixed or is rather a warning?

[paoloricciuti]

Just wondering about the severity of

Uncaught Error: Your application, or one of its dependencies, imported from 'svelte/internal', which was a private module used by Svelte 4 components that no longer exists in Svelte 5. It is not intended to be public API. If you're a library author and you used 'svelte/internal' deliberately, please raise an issue on https://github.com/sveltejs/svelte/issues detailing your use case.

in

svelte/packages/svelte/src/motion/tweened.js

Line 10 in 7ce2dfc

import { get, render_effect } from 'svelte/internal/client';
as this is thrown in other packages robinscholz/svelte-inline-svg#48 as well. Must it be fixed or is rather a warning?

You just can't import from that module. If you are not importing from that module and none of your dependencies does please provide a reproduction so we can look into it

[Konfekt]

This might take a while. I tried to convert a Legacy Snowpack repo to a Vite Svelte 5 one and at one point this occurred; since then I've taken steps back and try to go Vite Svelte 4 as an intermediary step

[7nik]

That library uses the private API for forwarding all events. But, in Svelte 5, spreading props is used for this.

[adiguba]

The InlineSvg component can be ported to Svelte 5 quite easily : Example in REPL

[dummdidumm]

Closing since there's nothing actionable here - code using those imports needs to be migrated