I suspect this was fixed in #53 for Svelte as well? I'll close this issue, if it's actually fixed then we could reopen the issue.

@eirslett I'm still experiencing this issue in 0.0.12

Some fixes for svelte were just released. Would folks here like to try out https://github.com/eirslett/storybook-builder-vite/releases/tag/v0.1.16 to see if hot reloading is improved for you, and report back? Thanks!

I'm using latest versions of builder-vite, svelte, @storybook/svelte and can confirm this is still an issue only for stories. When I make a change in a svelte component, HMR seems to be working fine.

Thanks for mentioning this, @vish01. I confirmed it's still an issue in our svelte example. I think it's similar to the problem we had with HMR for react components, where we needed to exclude the story files from being HMR boundaries. I've opened a feature request with vite-plugin-svelte to hopefully add an option that lets us customize the HMR boundaries similar to react.

For now, the only workaround I can think of is to provide this in your svelteOptions of .storybook/main.js:

  svelteOptions: {
    preprocess: preprocess(),
    hot: false, // <-- cause page reloads all the time
  },

EDIT You shouldn't need this ^ workaround with version 0.1.33 or higher.

@vish01 Can you please try out the latest version https://github.com/storybookjs/builder-vite/releases/tag/v0.1.33 and let us know if this solves the issue for you?

Hey @IanVS. I just tried out the 0.1.33 version, it kinda acts like the hot:false option(The UI for the component reloads, not the entire page), but I still don't see HMR work for stories. It still works for changes made in components though.

Hi thanks for checking it out. Unfortunately, that's the best we can do right now, and it's the same experience in react as well. Component changes can HMR, but story file changes require a refresh, due to the storybook manager also watching story files for HMR of the sidebar (list of stories).

At least the stories update without requiring a page refresh now, so hopefully a bit better than before.

Stories do refresh when using the latest version of builder-vite, but code changes made to stories still doesn't work until I reload the page myself or set the hot:false option. I'd still keep this issue open since HMR is still broken for stories or open a new issue if we want to separate our stories from components since it works fine with components.

code changes made to stories still doesn't work until I reload the page myself or set the hot:false option.

Oh I see, I misunderstood what you were saying earlier. Any chance you could provide a minimal reproduction so I can troubleshoot further?

@IanVS While creating repro, I found that the issue seems to be happening only when you modify Tailwind classes as props in stories. If I modify normal props like string, object, those seems to be working fine. Here's the repo since you wanted a minimal repro:
Storybook HMR repro
When you serve storybook, modify Card.stories.svelte and if you modify any of the justifyXXX props, you'll see it doesn't gets reflected in Storybook UI, but if you choose from the controls within the UI, it will change.

Thanks for explaining. I've tested out your example, and I find that as long as I don't change any of the controls in the story, I can edit any of the args, including the justify args, and they are reflected without having to refresh the page. However, if I change a control, and then try to also change the arg in the story file, then things break. But, this also happens in the webpack builder too, so I think it's a bug within storybook itself.

I also see that query params are being added to the url like &args=justifyHeader:right;justifyTitle:!undefined;justifyDescription:!undefined, which there's a PR to fix in storybookjs/storybook#17973. That takes care of the !undefined issue, but it seems that it still won't be possible to update story args that have been put into the url (in both webpack and vite). I don't see any open issue for that. If you're willing to open one, pointing to the reproduction repo, that would be excellent.

I'm going to re-close this issue for now, but if you think this is a vite-builder specific issue, please let me know. Thanks again for bringing this up, and for the reproduction steps.

Sounds good, I'll create a new issue on Storybook then. Thanks on checking this for me!