Manifest.json cause 404 error if file in resources is missing about horizon HOT 5 CLOSED

We also updated to the latest Horizon version (5.24.1) and this only seems to be an issue on local environments when running npm run dev since #1413. I have a bit more info from debugging:

The issue seems to be that when you run npm run dev it will use a different path (from the application's vite.config.js) and attempt to resolve the Horizon dependencies from the resources directory instead of vendor/horizon. If you don't run npm run dev then the assets will load correctly again.

While the layout loading the assets with Vite:asset() correctly passes the build directory, this is ignored when running in "hot" mode (which is what npm run dev does).

from horizon.

Did you publish the new assets like: https://github.com/laravel/laravel/blob/11.x/composer.json#L39

php artisan vendor:publish --tag=laravel-assets --ansi --force

from horizon.

@mmachatschek Should we possible use a different name for the manifest file? Like horizon-manifest? #1415

from horizon.

Reverted everything for now. Thanks all for reporting.

from horizon.

thanks @bramdevries thanks for the debugging info. Will check that

from horizon.