Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

gpapamichelakis's avatar

Laravel new with older version ?

Hey guys , I just realized that with the laravel installer is impossible to make a new project with the previous version ? ( I want to make a new project with version 12 with vue starter kit ) and is also impossible to add a starter kit to a existing composer installed 12 project ? Anyone has an idea if that is doable ?

1 like
12 replies
vincent15000's avatar

Hmmm ... why would you need to create a new application with an older version ?

Due to security reasons, the last version is more secure that the older ones.

Glukinho's avatar

Packages dependency issues probably.

1 like
vincent15000's avatar

If you create a new application, you depend on the new packages, so where is the problem ? There isn't any problem ;).

Glukinho's avatar

What if you need a package which is not tuned for Laravel 13 yet? Then you have to use 12 or even older versions.

1 like
DigitalArtisan's avatar

You then find another maintained package that works with Laravel13, or you fork the old package and make it work with Laravel13.

In any event, you eventually will have outdated Laravel 12 and packages in the future, actually now if that is the route you take.

Better off future proofing now, not later.

You have 2 months of active support today with Laravel 12.

1 like
Glukinho's avatar

will have outdated Laravel 12 and packages

So what? Not all apps are required to be up to date and not all are even publicly accessed. Sometimes it's more important to have running app right now rather than playing with forking someone's packages.

1 like
vincent15000's avatar

This can effectively be a good reason ;).

But I prefer in this case choose the last version of Laravel and find another package for the specific functionality.

I already did like this.

I did an upgrade of an application for a client. And a package I used wasn't compatible with the latest version of Laravel. I have removed the uncompatible package and I have written the code to have the same functionality.

gpapamichelakis's avatar

@martinbean Ok I tried to follow some info based on 12 to do something , I think it was ziggyvue only to find out that in 13, the installation instructions were not the same as some files changed . I get it , new versions of laravel are more secure etc but then it's frustrating trying to fish out what you need to change each time to make it work from one version to another , OK if I was in 8, but 12 to 13 ?

1 like
vincent15000's avatar

All Laravel versions are compatible with Ziggy.

The installation of Ziggy is simply not so detailed and is sometimes difficult to install and integrate into your application.

Max100's avatar

Fwiw, if you install version 12 with composer, you can then install Breeze which, if you chose the correct option, will install vue, inertia and ziggy. Just follow the instructions in the earlier docs (maybe back to v.11).

If you just want to avoid the latest starter kit, I have one with vue and inertia, without the newest starter kit features (shadcn and wayfinder). It uses fortify, laravel 13, inertia and vue with ziggy and daisyui instead of wayfinder and shadcn. But that won't help if you need Laravel 12.

For Laravel 12, try installing Breeze.

1 like
vincent15000's avatar

For Laravel 12, why installing Breeze instead of Fortify ?

And why not Laravel 13 ? As already mentioned, and also mentioned in all security articles, you should always use the latest version of your technologies.

Please or to participate in this conversation.