How to use older version of starter kit on "laravel new myapp"?
I dont want use this new feature of starter kits that use Fortify that happend at last month.
How i should use version of starter kit before this change?
If I use "composer install" to use Laravel 12.30 it doesn't show starter kit selection.
and with "laravel new newapp" i can't tell it to use version of 2 months ago.
how I should use Laravel 12 starter kit without all these Fortify stuff?
I found --using flag for installing other starter kits.
Why we can't give the --using same livewire-stater-kit but with older update?
Many users need something like this, why they didn't consider this?
Am I missing somthing here? is there another way to do it?
Fair enough. I've not tried any of the new starter kits as they don't interest me.. but wonder if a specific version can be pulled into a new project with a composer install?
@jlrdw I read somewhere (I think) they changed a bunch of auth/controller stuff, which does away with the auth routes as they used to be included and the likes of LoginController and RegisterController etc.. not sure what benefit that brings tbh.
Sometimes, I get the impression they're "bored".. but have to be seen to be making some kind of change to maintain "progression".... sometimes, something is simply.............. done.
after adding 2FA to starter kits, they use Fotrify for all auth logics and removed all auth controller.
I used to old stuff in all these years. i dont have time to learn f..ing Fortify.
It's last update of Livewire starter kit (without Volt) before Fortify stuff.
install regular Livewire starter kit on your project.
copy and replace all folders like app, routes, tests ... from downloaded older version to newly installed app.
delete Fortify from everywhere. like configs, composer.json and do these commands: