Closed mmachatschek closed 4 months ago
Hey @mmachatschek - can you explain what about this solution is "suboptimal"?
@taylorotwell suboptimal in the sense of having to pass in a non existent vite hotfile
name in the view to work around the vite helper not being able to detect that the vendor/horizon
assets were already published, as it's been pointed out here: https://github.com/laravel/horizon/issues/1416#issuecomment-2060505259
Please note that this caused an issue: https://github.com/laravel/horizon/issues/1439
Should at least use base_path
or similar rather than a root dir slash in layout.blade.php to find your non existent file.
Fixes #1416
This readds the vite implementation to bundle the assets with a fix to support
npm run dev
mode on the side of consuming laravel apps.Previously, the horizon page was broken because the Vite blade helper and the Vite Facade helper do not take into account that prebuilt assets by "third party" (in the sense of assets loaded by packages) packages should not be treated as uncompiled assets from the same laravel app.
The workaround here is suboptimal as I think the Vite blade helpers and the Vite Facade don't take into account that packages may also use these helper methods to render tags.