Svelte 5: How to replace <script context="module"> comprehensive ?

[qupig]

I'm not sure I've read all the documentation on Svelte 5.
But the only description I can find is:
https://svelte.dev/blog/runes#simpler-times-ahead

Runes are an additive feature, but they make a whole bunch of existing concepts obsolete:

• ...
• different behaviour between <script> and <script context="module">
• ...

What exactly has become of <script context="module"> in Svelte 5? What has it been replaced?

• What different behavior? Specific ones or all? Does it same as <script> in Svelte 5?
• Or does it retain the same behavior as in Svelte 4 when Runes mode is not enabled?
• Specifically, it still runs once when the module first evaluates? Are variables still persisted across instances?
• If NOT, what to do with variables that you want to persist across component instances?
  • Must it be imported from an external *.svelte.js file?
• Is the original import syntax import Example, { alertTotal } from './Example.svelte' still valid?
• What exactly does this error mean? Svelte 5: (non-state-reference) moduleVariable is updated, but is not declared with $state(...)...  #11269
• Please add some examples in the documentation to let us know how to replace them?

[brunnerh]

The module script is not being replaced as far as I know and probably shouldn't really be in that specific listing.
All its functions are still there.

The main behavior difference in v3/v4 is that variables in the module script are not reactive, this is not the case with runes.

[qupig]

difference in v3/v4 is that variables in the module script are not reactive

I don't believe this is true, based on the time of release: Announcing Svelte 4 (Jun 22 2023)

And the note was added to the document around June-July 2019:

Variables defined in module scripts are not reactive — reassigning them will not trigger a rerender even though the variable itself will update. For values shared between multiple components, consider using a store.

In fact, they still made some relevant changes in v4.2.1: #9122

Regarding Runes, yes, a throwback? I don't know, there isn't any documentation to refer to.

[brunnerh]

I did not say that there is a difference between v3 and v4, but that the difference noted in the blog ("different behaviour between <script> and <script context="module">") is the lack of reactivity in the module script which is in both v3/v4 and not in v5 with runes.

One of the main points of runes is to unify reactivity so it works in component scripts, component module scripts and even regular JS modules (with .svelte.js/ts extension).

[qupig]

Okay, that makes sense. It actually means that variables defined in <script> also loses reactivity in favor of a uniform use of Runes.
Thank you for the explanation. I would still like to see more accurate and clear documentation added.