Laravel Installer as part of the Framework

[Jubeki]

Hey everybody!

I had the idea to replace the laravel installer with a framework option, that is also triggered when running for example:

composer create-project laravel/laravel example-app

It would be achieved with the following in the skeleton:

{
    "name": "laravel/laravel",
    "type": "project",
    "description": "The skeleton application for the Laravel framework.",
    "keywords": ["laravel", "framework"],
    "license": "MIT",
    "scripts": {
        "post-create-project-cmd": [
            "@php artisan key:generate --ansi",
            "@php artisan laravel:install --ansi",
            "@php -r \"file_exists('database/database.sqlite') || touch('database/database.sqlite');\"",
            "@php artisan migrate --graceful --ansi"
        ]
    }
}

(See the additional php artisan Laravel:install --ansi)

And then a copy of the laravel/installer into laravel/framework as a new Command.

What are the advantages of this approach?

• The installer will always be up to date with the framework.
• No manual update of the installer with composer global update laravel/installer.
• The installer will be installed with the framework, so no need to install it globally.
• The installer can be used on older laravel versions. (verifiying bugfixes with Laravel 10 for example.)
• Everybody gets access to the nice installation options which you can select.

What are you opinions on that approach?