Svelte 5: Preserve local state during HMR

[bhuynhdev]

Describe the bug

With a brand new SvelteKit project with Svelte 5, I realized that all my states are reset whenever HMR updates

Whenever I change anything in the HTML part of a Svelte file, HMR kicks in and resets all my $state, which makes it very cumbersome to develop a large and complex form

I read that earlier version support directives such as @hmr:keep-all or preserveLocalState, but according to sveltejs/kit#12985, these are outdated and no longer used

So I am unsure what to do now to preserve states between HMR reloads - is this a bug or a feature request?

Reproduction

Reproduction link in SvelteLab: https://www.sveltelab.dev/63iv5zkf3ed2806

Steps to reproduce:

1. Check the checkbox
2. Click the button
3. Change something in the HTML, like adding more text to the paragraph
4. All states get reset - the checkbox gets unchecked, and text resets to initial value 🚩

Logs

No response

System Info

System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
    Memory: 13.97 GB / 14.90 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 23.3.0 - ~/.local/share/mise/installs/node/23/bin/node
    npm: 10.9.0 - ~/.local/share/mise/installs/node/23/bin/npm
    pnpm: 9.14.2 - ~/.local/share/mise/installs/node/23/bin/pnpm
  npmPackages:
    svelte: ^5.1.13 => 5.1.13

Severity

annoyance

[apekros]

Also just ran into this issue with tauri+Svelte 5, would love to have something like the directives or preserveLocalState support

[dominikg]

you can add this code to the end of your script block to manually preserve the checked state

	if (import.meta.hot) {
		if (import.meta.hot.data.checked != null) {
			checked = import.meta.hot.data.checked;
		}
		import.meta.hot.accept();
		import.meta.hot.dispose(() => {
			import.meta.hot.data.checked = checked;
		});
  }

It may be possible to extend the svelte compiler to parse annotations and create this code for you, however it should always be used as a scalpel.

[ngoov]

Are there any plans to add this to the kit configuration? It's a shame that by replacing svelte-hmr and vite's default HMR, SvelteKit does not support this functionality anymore. It's kind of a step backwards IMO.

And adding code at the end of a script block to keep track of all the client state is not feasible...

[Saltallica]

I agree - HMR not preserving state loses much of its usefulness. It is intended to be a productivity tool.

if I can't adjust my HTML and see the output applied to the existing state, it's no better than just reloading a page and starting over.

There is no way in hell I am bolting in a bunch of stuff for every component for what should be provided out of the box.

[dominikg]

It's a shame that by replacing svelte-hmr and vite's default HMR, SvelteKit does not support this functionality anymore. It's kind of a step backwards IMO

this was never a default feature of vite hmr, the code I posted above is what you have to do to preserve local state in vite hmr.
svelte-hmr had a custom implementation to automate some of this for you, but it comes with the caveats described in
svelte-hmr readme and was disabled by default.

If state reset is getting in the way of your dx, in some cases it can be a sign that the state shouldn't be local to that component but instead held in a different module. If you refactor it and pass it in via prop, the value will be preserved when the component updates.

[darkstarx]

Compared to Flutter, it's terrible. The state of the component should not be reset while editing its html code out of the box.

[ngoov]

It's a shame that by replacing svelte-hmr and vite's default HMR, SvelteKit does not support this functionality anymore. It's kind of a step backwards IMO

this was never a default feature of vite hmr, the code I posted above is what you have to do to preserve local state in vite hmr. svelte-hmr had a custom implementation to automate some of this for you, but it comes with the caveats described in svelte-hmr readme and was disabled by default.

If state reset is getting in the way of your dx, in some cases it can be a sign that the state shouldn't be local to that component but instead held in a different module. If you refactor it and pass it in via prop, the value will be preserved when the component updates.

I guess I was comparing it to React's Fast Refresh then, my bad. It does this OOTB for every component change.

[FluffyDiscord]

This is stupid. Svelte 3 and 4 handled that beautifully. It was THE reason go with Svelte. Why it's not in Svelte 5?

[paoloricciuti]

This is stupid. Svelte 3 and 4 handled that beautifully. It was THE reason go with Svelte. Why it's not in Svelte 5?

First, please be more polite. Second: hmr that persist state was your only reason to use svelte? 😁

[FluffyDiscord]

Second: hmr that persist state was your only reason to use svelte? 😁

Have I stated, that it was the only reason? I am sure I didn't. I know that reading is hard. We all fail, some fail harder apparently.

[paoloricciuti]

Glad to see you skipped the being polite part and instead doubled down with very inappropriate comments. Furthermore all cap THE is usually referring to that being the only/main reason.