It is important! Hence why I am here watching this video! XD

Pretty cool indeed!

It is normal. In real life nobody will see your token as it is transferred encrypted with all other HTTPS traffic. This is why you should always use HTTPS in public Internet.

And anyone reading this, DONT mess with CSRF. Its just not relevant for Livewire.

For anyone who may come across this in the future: it all went wrong when I set up UUID on my Users table. I didn't also update the sessions table foreign key to look for a UUID. WOW that was frustrating but I hope this helps someone.

I found this on the Livewire Install page:

https://livewire.laravel.com/docs/3.x/installation#manually-bundling-livewire-and-alpine

/livewire/livewire.js returning a 404 status code
By default, Livewire exposes a route in your application to serve its JavaScript assets from: /livewire/livewire.js. This is fine for most applications, however, if you are using Nginx with a custom configuration, you may receive a 404 from this endpoint. To fix this issue, you can either compile Livewire's JavaScript assets yourself, or configure Nginx to allow for this.

Hi guys.

If I run php artisan route:list I see the following in the response:

GET|HEAD   flux/editor.css generated::2bgScuHRO1iqIrjM › Flux\AssetManager@editorCss › AssetManager@editorCss
  GET|HEAD   flux/editor.js ... generated::E7Gn0gDkt8QICUgE › Flux\AssetManager@editorJs › AssetManager@editorJs
  GET|HEAD   flux/editor.min.js generated::SZnULyhA6rducCgw › Flux\AssetManager@editorMinJs › AssetManager@edit…
  GET|HEAD   flux/flux.js ......... generated::ahqtW0rAdXPfR0qO › Flux\AssetManager@fluxJs › AssetManager@fluxJs
  GET|HEAD   flux/flux.min.js generated::Hy1dWeEnCyqTwNRG › Flux\AssetManager@fluxMinJs › AssetManager@fluxMinJs
  GET|HEAD   forgot-password ........... password.request › Laravel\Fortify › PasswordResetLinkController@create
  POST       forgot-password .............. password.email › Laravel\Fortify › PasswordResetLinkController@store
  GET|HEAD   livewire/livewire.js generated::uKJLeWpZdaVXwjig › Livewire\Mechanisms › FrontendAssets@returnJava…
  GET|HEAD   livewire/livewire.min.js.map generated::XBE42vFZ8SnO1v8F › Livewire\Mechanisms › FrontendAssets@ma…
  GET|HEAD   livewire/preview-file/{filename} livewire.preview-file › Livewire\Features › FilePreviewController…
  POST       livewire/update ............... livewire.update › Livewire\Mechanisms › HandleRequests@handleUpdate
  POST       livewire/upload-file ....... livewire.upload-file › Livewire\Features › FileUploadController@handle
  GET|HEAD   login ............................. login › Laravel\Fortify › AuthenticatedSessionController@create

I am just wanting to double check with all the Livewire users out there that this is normal that if I go to my website URL/livewire/livewire.js I should be able to see the URL publicly... I just found it weird that I could go to the URL at all.

Thanks guys!