You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing out Inertia with Vue, and I've noticed, that making any changes to the inertia\css\app.css file will throw the [vite] css hmr is not supported in runtime mode error in the console, while still reflecting the changes in the browser window. Not sure how to fix this error.
To reproduce:
Initialize Adonis app with Inertia Starter Kit, choose Vue adapter, and set server-side rendering with Inertia to true. Once the dev server is running, any changes you make to the app.css file will trigger the error.
Reproduction repo
No response
The text was updated successfully, but these errors were encountered:
I see. Is there a way to hide this warning? Because it's cluttering the console a lot, especially since sometimes it writes the same message 3+ times in a row after a single save.
I've noticed, that it doesn't happen if I don't touch the refresh button of the page. It works fine without any warnings. However after refreshing the page, it starts appearing.
It seems that HMR watcher gets duplicated after page refresh, and they probably start conflicting with eachother. Even the warning message appears as many times (+1), as the page was refreshed further proving this conclusion.
Package version
1.1.0
Describe the bug
I've been testing out Inertia with Vue, and I've noticed, that making any changes to the
inertia\css\app.css
file will throw the[vite] css hmr is not supported in runtime mode
error in the console, while still reflecting the changes in the browser window. Not sure how to fix this error.To reproduce:
Initialize Adonis app with Inertia Starter Kit, choose Vue adapter, and set server-side rendering with Inertia to
true
. Once the dev server is running, any changes you make to the app.css file will trigger the error.Reproduction repo
No response
The text was updated successfully, but these errors were encountered: