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
When running this plugin with Vite v6, the name of the generated asset appearing in my Vite manifest file no longer is the 'static' webfonts.css, but rather matches the emitted filename including hash; e.g. _webfonts-CA-ApsEA.css.
This means when paired with Laravel and loading with @vite('webfonts.css'), an error is Unable to locate file in Vite manifest: webfonts.css. is thrown.
(Note: I've glanced through the migration guide but could not find a logical culprit myself. This issue is short; I hope to find some time to elaborate further at some point, but maybe from my limited context it's already possible to reproduce and solve this with more knowledge of Vite internals).
The text was updated successfully, but these errors were encountered:
When running this plugin with Vite v6, the name of the generated asset appearing in my Vite manifest file no longer is the 'static'
webfonts.css
, but rather matches the emitted filename including hash; e.g._webfonts-CA-ApsEA.css
.This means when paired with Laravel and loading with
@vite('webfonts.css')
, an error isUnable to locate file in Vite manifest: webfonts.css.
is thrown.A minimal reproduction of that on basic Laravel setup can be found at https://github.com/jnoordsij/laravel-laravel/compare/webfont-dl-mwe:
(Note: I've glanced through the migration guide but could not find a logical culprit myself. This issue is short; I hope to find some time to elaborate further at some point, but maybe from my limited context it's already possible to reproduce and solve this with more knowledge of Vite internals).
The text was updated successfully, but these errors were encountered: