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 creating a new Laravel project with Jetstream on Windows machines, after running npm run build to compile the Vite assets, the public\build\manifest.json is being generated with wrong backslashes in the CSS path, as you can see in the following image, and causing the following exception:
Unable to locate file in Vite manifest
The issue was confirmed on Windows 11 and Windows 10 machines. It was also tested on a Linux machine with Ubuntu 20.04, but the problem doesn't happen.
It started happening this week, as projects created until last week were correctly generating the manifest.json file.
The issue doesn't happens when creating a new Laravel project without Jetstream
Steps To Reproduce:
1 - Create a new Laravel project with Jetstream/Livewire (maybe using laravel new project --jet) on a Windows machine
2 - Run npm run build to compile the Vite assets
3 - Open the file public\build\manifest.json to see the backslashes
Description:
When creating a new Laravel project with Jetstream on Windows machines, after running npm run build to compile the Vite assets, the public\build\manifest.json is being generated with wrong backslashes in the CSS path, as you can see in the following image, and causing the following exception:
The issue was confirmed on Windows 11 and Windows 10 machines. It was also tested on a Linux machine with Ubuntu 20.04, but the problem doesn't happen.
It started happening this week, as projects created until last week were correctly generating the manifest.json file.
Steps To Reproduce:
1 - Create a new Laravel project with Jetstream/Livewire (maybe using laravel new project --jet) on a Windows machine
2 - Run npm run build to compile the Vite assets
3 - Open the file public\build\manifest.json to see the backslashes
Related Issues
TiagoSilvaPereira/vemto-issues#351
laravel/vite-plugin#19
The text was updated successfully, but these errors were encountered: