Vite application manager

[daniser]

Currently Vite helper is a singleton which mean that it may hold only one configuration at a time, allowing developer to customize only entry points and build directory per __invoke call. This may cause problems in multi-app configurations.

Example
In our project we use many SPAs within mainly legacy codebase. We manage our apps using Yarn workspaces. Axios, Echo and Ziggy configurations are shared between apps and stored in resources/js/bootstrap.js (resources/js/app.js entry point), as suggested by Laravel. This bootstrap code is injected into main page layout and accessible throughout the entire project and all its sub-apps.
The problem arose when it became necessary to debug specific app using yarn dev (vite) command to serve its assets. Vite can't serve multiple applications at once, so we need to use separate hot files for each application. But Laravel's Vite helper can only hold one configuration... so here we are.

Reasoning

• allow Vite helper to manage multiple app configurations;
• take app configuration out of Blade templates and store it in centralized location;
• add support for app factory so new apps can be added without need to configure them separately;
• make it possible to configure default "app" for each environment separately via VITE_APP environment variable.

Backward compatibility
Vite facade, Vite helper injection and @vite Blade directive should work as before, but instead of resolving singleton from application's container, they will point to "default" entry from the ViteManager.
Vite contract has been added to allow ViteManager to implement it.

Configuration
There are 3 ways to configure Vite "apps":

1. config/vite.php file (should probably be added into laravel/laravel repo?):

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Vite App
    |--------------------------------------------------------------------------
    */

    'app' => env('VITE_APP', 'default'),

    'apps' => [

        'default' => [
            'entry_points' => ['vite/legacy-polyfills-legacy', 'resources/js/app-legacy.js', 'resources/js/app.js'],
            'build_directory' => 'build',
        ],

        'myapp' => [
            'entry_points' => ['vite/legacy-polyfills-legacy', 'src/app-legacy.js', 'src/app.js'],
            'build_directory' => 'build/packages/myapp',
            'hot_file' => 'build/packages/myapp/hot',
        ],

    ],

];

2. Service provider's boot method:

<?php

namespace App\Providers;

use Illuminate\Support\Facades\Vite;
use Illuminate\Support\ServiceProvider;
use Illuminate\Support\Str;

class ViteServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Vite::withEntryPoints(['vite/legacy-polyfills-legacy', 'resources/js/app-legacy.js', 'resources/js/app.js'])
            ->useBuildDirectory('build');

        Vite::app('myapp')
            ->withEntryPoints(['vite/legacy-polyfills-legacy', 'src/app-legacy.js', 'src/app.js'])
            ->useBuildDirectory('build/packages/myapp')
            ->useHotFile(public_path('build/packages/myapp/hot'))
            ->useScriptTagAttributes(function (string $src) {
                return Str::contains($src, '-legacy') ? ['type' => 'text/javascript', 'nomodule'] : [];
            })
            ->usePreloadTagAttributes(function (string $src) {
                return Str::contains($src, '-legacy') ? ['rel' => 'dummy'] : [];
            });
    }
}

3. App factory:

<?php

namespace App\Providers;

use Illuminate\Contracts\Foundation\Vite as ViteContract;
use Illuminate\Support\Facades\Vite;
use Illuminate\Support\ServiceProvider;
use Illuminate\Support\Str;

class ViteServiceProvider extends ServiceProvider
{
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Vite::useAppFactory(fn (ViteContract $vite, string $app, array $config) => $vite
            ->withEntryPoints(['vite/legacy-polyfills-legacy', 'src/app-legacy.js', 'src/app.js'])
            ->useBuildDirectory("build/packages/$app")
            ->useHotFile(public_path("build/packages/$app/hot"))
            ->useScriptTagAttributes(function (string $src) {
                return Str::contains($src, '-legacy') ? ['type' => 'text/javascript', 'nomodule'] : [];
            })
            ->usePreloadTagAttributes(function (string $src) {
                return Str::contains($src, '-legacy') ? ['rel' => 'dummy'] : [];
            })
            // amend/fall back to config entry for the app (if exists) from the "config/vite.php" file
            ->configure($config)
        );
    }
}

Usage
@viteApp directive should be used in Blade templates to enjoy the power of multiappness to its fullest:

<!-- Shared bootstrap code -->
@viteApp

<!-- Example app -->
@viteApp('myapp')

Testing
I should probably add some tests for this feature, but I'm not good at it, so any help will be appreciated.
For now, I'll mark this PR as draft and try to write some tests.

[taylorotwell]

I wonder if this could be written as a package for your own usage purposes? It feels a bit like a niche case to add more complexity to our own code base and maintenance burden for.