WDS as Middleware with refresh on file change. about web HOT 5 CLOSED

Locally I can hack the configs to pass the devServer from Storybook to new DevServer() in startDevServer.js, and it will allow for refreshing the page, but only up until some React error that that causes crashes the page. 🤔

from web.

IIRC it required more logic and integration code for the Storybook, so I made a separate task in the future and focused on basic functionality. It's still planned.

Meanwhile I'm curious what exactly you expect to work?
Some sort of HMR? Or just page refresh?

from web.

The baseline would be auto page refresh much like WDS does in other cases with

webSockets.sendImport('data:text/javascript,window.location.reload()');

I'm not one for a lot of ceremony on this, but being we've received it in so many other contexts, it's hard to get away from this sort of a feature when suggesting tools like this to a team.

It would be interesting to see actual HMR included...but, I've never seen it really work, so it wouldn't be me pushing for it by any means. I'm not even sure if the HMR tools that OpenWC was working with ever actually got updated to [email protected] let alone the upcoming [email protected] release.

Practically, the vite builder accepts the Storybook devServer into its config, so there is likely a path to make the baseline of what I was trying work, I just don't know how to debug the issue that it causes in Storybook's React UI. 😞

from web.

@Westbrook thanks for your feedback. I agree we need to implement the baseline, I think the previous storybook-prebuilt setup had smth like that, and also not a real HMR. I hope to pick this up soon.

from web.

This seems like the laziest possible path: #2482

from web.