livewire VS inertia-laravel

No its not, Livewire 3 is still getting a fair few bug reports, there was a pretty significant one last week too. Best to keep an eye here: https://github.com/livewire/livewire/discussions

That event.stopImmediatePropagation() will stop the Livewire method from being called, if the confirmation result is false. You may find a few other possible solutions in https://github.com/livewire/livewire/issues/366

10. livewire/livewire

There were some big pagination changes in 2.6, I would install a version before that and see if you get your desired results back, if so, you just need to figure out what the change was in 2.6 that broke it and update.

https://github.com/livewire/livewire/issues/242#issuecomment-616501502

Livewire's creator here. This problem is so bonkers and such a pain to deal with.

For your amusement. Here's the code that was SUPPOSED to fix the bug: https://github.com/livewire/livewire/blob/0b3feda46a9dd6ad19...

https://github.com/livewire/livewire/blob/0b3feda46a9dd6ad19...

And here's the podcast I recorded a while back on what a pain it is: https://laravel-livewire.com/podcasts/ep65-safari-sucks-here...

This is (as far as I know) not documented and I had to dive into the sourcecode for both the inertia server runner and the Laravel command to start the server to understand what is going on. Here we go.

So here is a quick guide how to set up a new Rails 7 app using my favorite projects out there: Inertia and Svelte. You can also skip all this and download the endresult directly from here: https://github.com/buhrmi/rails7-starter

Might be interested in https://inertiajs.com/

Laravel Viltify is a heavily opinionated Laravel starter kit. It's intent is to seamlessly integrate Vue, Inertia.js, Laravel, TailwindCSS and Vuetify, so you don't waste your time learning how to do it and focus on writing your application, leaving setup behind.

Can't believe nobody recommended inertiajs here!

I would recommend InertiaJS for using Vue.js with Rails. It lets Rails continue to handle navigation so you don't have to replicate it client side. Same thing with views which gives you a very nice balance between an SPA and a fully server rendered app.

Now more than ever, it has become very easy to integrate React in your Laravel project, as opposed to before when one had to depend on APIs to connect the two stacks. This meant two different hosting environments and two Git repos to manage. But with InertiaJS we can build SPAs (single page apps) with your preferred front-end in one single project without need for APIs. Inertia has support for React, Vue or Svelte to use in your front-end. You pass data in your controllers as in any ordinary Laravel project, only difference is you're now rendering your views as JavaScript elements instead of blade. This can be done in two ways:

Awesome. I’m noticing a ton of “alternative” front end development tools these days: Hotwire, Stimulus Reflex, LiveView, Livewire, etc.

However I don’t think javascript is the fundamental blocker. When people say they dislike building SPAs, they probably mean they dislike APIs and the whole circus of double validations, error catching, form handling and cache invalidations that come with a React/Vue SPA.

Inertiajs[1] is a really solid middle ground of MVC goodness and client side interactivity.

[1] - https://inertiajs.com