-
Notifications
You must be signed in to change notification settings - Fork 155
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
CSS file paths in Vite 3 manifest broken on Windows #101
Comments
Using Windows? |
Please fill out the FULL issue template. |
Yes, using Windows |
Can you please fill out the remaining parts of the issue template?
|
I have updated it. |
Hi, same error for me after updating to plugin version 0.5.0 and vite 3.0.2 Laravel Vite Plugin Version: 0.5.0 Found this issue to the error: |
Hi @AhsanAbrar, As of version 3, Vite is now responsible for adding CSS files to the manifest. In version Therefore it seems like this is an issue with Vite 3 rather than this plugin. If you're using a front-end framework like Vue, then I would recommend importing your CSS via JavaScript instead of having a CSS entry point. Be sure to also update your Otherwise, I would suggest using Vite 2 with version |
Thanks @jessarcher |
I've opened a PR to address this in Vite. I would absolutely love if someone could test this fix for me as I cannot actually test this fix locally. See: vitejs/vite#9353 |
The fix for this has been merged upstream and I assume will be tagged in Vite |
Please update to the latest version and this issue should be resolved for you. See: https://github.com/vitejs/vite/blob/v3.0.4/packages/vite/CHANGELOG.md |
@timacdonald You did a great job! Thanks |
Thanks for the fix! It worked!!! |
Glad it is sorted for you, folks! |
Description:
After running this command:
Getting this error:
Steps To Reproduce:
I have done some research on it.
there is an issue in the
manifest.json
file.and in the
Vite.php
this manifest key is not matching.that's why
js
files working fine andcss
files having issues.please fix this, thanks.
The text was updated successfully, but these errors were encountered: