laravel/vite-plugin-wayfinder is creating multiple exports with the same name

[theHocineSaad]

Bug description

I have a fresh Laravel app using the React starter kit, which comes with laravel/vite-plugin-wayfinder installed and configured, which is a Vite plugin for Wayfinder.

One of the things that Wayfiner does is generate importable TypeScript functions for routes, so in TypeScript, instead of doing something like href="/dashboard" we will be able to do href={dashboard()}.

It uses the name of the Laravel route to generate the TypeScript function, which is fine, but with the Tennancy for Laravel package installed, and as it is mentioned in the docs, we should add this to the web.php file:

foreach (config('tenancy.central_domains') as $domain) {
    Route::domain($domain)->group(function () {
        // your actual routes
    });
}

This will generate multiple routes with the same name (because we may have multiple central domains), and Wayfinder will create multiple exports with the same name, which is not possible in JavaScript:

Steps to reproduce

1. Create a new Laravel app and use the React starter kit.
2. Install Tenancy for Laravel by following the Quickstart Tutorial.
3. php artisan serve and npm run dev and visit the home page.

Expected behavior

Wayfinder should not create multiple exports with the same name.

Laravel version

12.44.0

stancl/tenancy version

3.9

[theHocineSaad]

One solution I can think of is adding a prefix to the route names per domain, so we will have:

• example_com.home
• example2_com.home

And we ignore APP_URL, so if we take example.com as the url in APP_URL, we will have:

• home
• example2_com.home

Code:

use Illuminate\Support\Uri;

$appDomain = Uri::of(config('app.url'))->host();

foreach (config('tenancy.central_domains') as $domain) {
    Route::domain($domain)
        ->name($domain != $appDomain ? str_replace('.', '_', $domain) . '.' : null)
        ->group(function () {
            Route::get('/', HomeController::class)->name('home');
        });
}

[stancl]

Wayfinder has several limitations that make it difficult to use with multi-tenancy at the moment. The issue you're submitting here is not actionable for us because there's nothing we can do in Tenancy to fix this. These things should instead be reported in the Wayfinder repo, preferably in a way that's not tied to this specific Tenancy package (for instance things relating to domain-scoped routes do not require Tenancy) so they be addressed by the Laravel team.