-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HMR broken in certain cases when using the Storyblok integration #4727
Comments
Hey @matthewp, should this issue theoretically be fixed with the new 1.2.4 release using Vite 3.1? I've just tested it but the issue remains. |
@manuelschroederdev No, @bluwy and I debugged it and there's another Vite bug that needs to be fixed. @bluwy is working on that now. |
Cool, thanks for your hard work! |
This one's a rollercoaster by I managed to fix it at vitejs/vite#10144 |
Looks like vitejs/vite#10144 is getting rather complicated to solve. 👀 |
@manuelschroederdev I've chat with patak today and got it resolved. It's planned for Vite 3.2, which the beta would release next week. So it might take a few weeks to reach stable. Is this currently blocking the Storyblok integration? If so, I can try to fast-path it as a patch release as I think it's a safe change. |
Hey @bluwy, that's great news, thanks! |
@manuelschroederdev Vite 3.1.3 is released with the fix! Will update astro to use it. |
Wonderful news, thank you 🙏 |
@bluwy is there still another fix coming in 3.2? Or is this the only one? |
Yeah this is the only one. I tested and Vite 3.1.3 fixes the Storyblok repro. |
What version of
astro
are you using?1.2.2
Are you using an SSR adapter? If so, which one?
NOne
What package manager are you using?
npm
What operating system are you using?
Mac
Describe the Bug
HMR doesn't seem to be triggering updates in components used by the Storyblok integration. Storyblok's API sends down JSON blocks that are mapped back to Astro components based on a
component
string keyI haven't had a chance to dig deeper into this one yet, but a few early thoughts
string -> component
mapping done inside the integration isn't being reflected in the dependency graph in Vite...is this an issue in Astro, the integration, or an API limitation?Link to Minimal Reproducible Example
https://stackblitz.com/edit/astro-sdk-demo
Participation
The text was updated successfully, but these errors were encountered: