My Nginx config automatically caches and optimises assets, such as livewire/livewire.js?id=e2b302e9.
This means a route which fakes the assets being available there, such as the one pulse uses, returns a 404.
In other projects I've been able to run php artisan livewire:publish to work around this, but in Pulse this does nothing. Would this be an option going forward?