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
Not sure if I'm missing something obvious here, but I'm using your package for a larger Vue3 project that has dynamic imports.
So $item = $manifest->data->{$entry} in load_production_asset() might have an array of dynamicImports.
These dynamic imports, in turn, have manifest entries that list CSS dependencies of their own.
I thought that Vite would have code to automatically load and inject this CSS into the page when the dynamic import is requested. It actually does so in development mode, but in production builds, those CSS files fail to load.
As a workaround, I'm currently using the vite_for_wp__production_assets WP filter to recursively scan and queue any potential dynamic CSS dependencies but I'm sure it must be a Vite build option that is set incorrectly that's causing the problem.
The text was updated successfully, but these errors were encountered:
Not sure if I'm missing something obvious here, but I'm using your package for a larger Vue3 project that has dynamic imports.
So
$item = $manifest->data->{$entry}
inload_production_asset()
might have an array ofdynamicImports
.These dynamic imports, in turn, have manifest entries that list CSS dependencies of their own.
I thought that Vite would have code to automatically load and inject this CSS into the page when the dynamic import is requested. It actually does so in development mode, but in production builds, those CSS files fail to load.
As a workaround, I'm currently using the
vite_for_wp__production_assets
WP filter to recursively scan and queue any potential dynamic CSS dependencies but I'm sure it must be a Vite build option that is set incorrectly that's causing the problem.The text was updated successfully, but these errors were encountered: