ziggy VS inertia-laravel

The Ziggy package, provides a Javascript helper that makes it very easy to generate Laravel route url's, in your frontend code, the code would look something like this:

5. tighten/ziggy

Inertia uses Laravel's routes, so we won't need to use a client side router, but to make use of Laravel's web.php routes, we have to pass them to the DOM somehow. The easiest way to do it to use Ziggy. Let's install Ziggy:

Hi! I am currently trying to get Ziggy to work with InertiaJS but I cannot get it to work at all. I can clearly see that Ziggy is included (using the @route directive in my blade file). When calling window.route() outside my Vue components it works fine. But when I try to call it inside my components I get this:

Inertia makes a lot of things trivial to do, like managing routes, and handling middleware on routes . Since it uses your routes file to create routes in the vue app (use https://github.com/tighten/ziggy and you can use named routes in your vue files too). Also form validation and showing any error messages is pretty easy. it returns an errors object from your controller, so you only have to maintain validation rules in one spot.

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