livewire.js gives 404 in production about pulse HOT 7 CLOSED

I had the same error and I have found the following fix:

• you need to install livewire via composer (composer require livewire/livewire)
• if you are using nginx as a webserver add the following lines to your config

location = /livewire/livewire.js {
    expires off;
    try_files $uri $uri/ /index.php?$query_string;
}

source: https://benjamincrozat.com/livewire-js-404-not-found

from pulse.

Hitting this issue as well.

It would seem that the js code loading part @livewireScripts returns a path from the root of the domain instead of taking into account the env's APP_URL... maybe?

In my case, the whole laravel part of the website is served under a subdirectory, so if I manually add this part, the .js gets found as expected.

from pulse.

Alright, this is mentioned in the docs: https://livewire.laravel.com/docs/installation#customizing-the-asset-url

That said, the default behaviour, once you composer require it, may lead people to think it's broken, which is unfortunate.

from pulse.

Pulse Version
v1.0.0-beta2

Laravel Version
10.34.2

PHP Version
8.2.10

In my case http://localhost:8000/pulse return 404

from pulse.

Thank you for reporting this issue!

As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub.

If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team.

Thank you!

from pulse.

Seems this isn't an issue with Pulse specifically, but a configuration issue of the consuming application.

Will close this and would welcome suggestions if there are improvements we can make here.

from pulse.

Opened a PR to address this moving forward: #266

from pulse.