Level 63
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.
May 27, 2026
8
Level 1
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 ?
Packages dependency issues probably.
1 like
Level 63
If you create a new application, you depend on the new packages, so where is the problem ? There isn't any problem ;).
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
Level 3
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
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
Level 63
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.
Level 80
@gpapamichelakis Why? You should always be using the most recent version of software.
1 like
Please or to participate in this conversation.