Does it make sense to move pure functions to a script module in Svelte 5?

[Serator]

In Svelte 4, the compiler hoisted pure functions even if they were not declared in script context="module". This was also mentioned in the documentation:

Don't worry that we're redeclaring the foo function for every component instance — Svelte will hoist any functions that don't depend on local state out of the component definition.

Demo / Svelte 4.0.0 (example from Svelte 4 documentation)

But in Svelte 5, this is no longer the case, and I can't find any mention of this change anywhere.

Demo / Svelte 5.46.0 (example from Svelte 4 documentation)

Demo / Svelte 5.46.0 as script module (example from Svelte 4 documentation)

[brunnerh]

Svelte 5 did have a lot more hoisting, but that was removed because it did not yield any significant benefits at the cost of making everything more complicated.

Would recommend measuring whether your example makes a difference in your specific case and only optimize if there is a reason to. E.g. depending on the number of instances it might be irrelevant anyway.

[Serator]

Got it, thanks.