Skip to content
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

Behavioral change with Vite v6 #65

Closed
jnoordsij opened this issue Dec 3, 2024 · 1 comment · Fixed by #66
Closed

Behavioral change with Vite v6 #65

jnoordsij opened this issue Dec 3, 2024 · 1 comment · Fixed by #66

Comments

@jnoordsij
Copy link
Contributor

jnoordsij commented Dec 3, 2024

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.

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant