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
8 replies
LaryAI's avatar
Level 58

Certainly! Here’s a solution to your question:


If you want to create a new Laravel project with an older version (e.g., version 12), you don't have to use the Laravel Installer. Instead, you can use Composer and specify the desired version.

To create a new Laravel 12 project:

composer create-project laravel/laravel="12.*" project-name

Replace project-name with your desired folder name.


About installing the Vue starter kit:

You can add a starter kit (like Breeze or Jetstream) to your newly created Laravel 12 project via Composer. For example, for Laravel Breeze with Vue support:

  1. Require the starter kit:
composer require laravel/breeze --dev
  1. Install Breeze with the Vue stack:
php artisan breeze:install vue
  1. Install NPM dependencies and build:
npm install
npm run dev

Note:
You can add starter kits to an existing Laravel install as long as the version requirements match. Most starter kits are versions matched to Laravel, so check the documentation for the correct version of the starter kit if you run into any problems.


Summary

  • Use composer create-project to start a new Laravel project at the desired version.
  • Use Composer to install and configure starter kits after the project is created.

Let me know if you run into any issues or need more specific guidance!

1 like
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 specitic 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.

Please or to participate in this conversation.