possibility to publish translations for packages not installed

[msdevcoder]

Feature description

a config option to list not installed packages there to get their translations published too would be nice.

use case: I'm writing own auth views for fortify, and wanted to use the translations from jetstream for the forms, but without jetstream installed they are not published, so no translation.

[andrey-helldar]

The opportunity is already there. There are two options.

Option 1: if translations need to be published always when your file package is installed in the application, then simply do not specify $vendor and $version properties in the plugin file.

Option 2: you can specify laravel/fortify as the name. For example.

[msdevcoder]

ehm, editing the package files in the vendor folder? they are not pushed to git and so not in the live project?

[andrey-helldar]

Uh, hold on. Why would they need to get into git?

Translation source files are not needed in production. That means you install them during development and run a command to publish them.

Do I understand correctly that you want to force the Fortify translations to be installed in your project?

If yes, then:

1. I agree to add the forced installation functionality (I don't know how soon I will do it).
2. there is an option to do “here and now”. Create the following files in your app (don't forget to register a service provider):

namespace App\Http\Providers;

use App\Translations\Plugin;
use Illuminate\Support\ServiceProvider;
use LaravelLang\Publisher\Plugins\Provider;

class TranslationsServiceProvider extends ServiceProvider
{
    public function register(): void
    {
        if (class_exists(Provider::class)) {
            $this->app->register(Plugin::class);
        }
    }
}

namespace App\Translations;

use LaravelLang\Lang\Plugins\Fortify\V1;
use LaravelLang\Publisher\Plugins\Provider;

class Plugin extends Provider
{
    protected string $base_path = __DIR__ . '/../vendor/laravel-lang/lang/';

    protected array $plugins = [
        V1::class,
    ];
}

[msdevcoder]

Thx for the quick hack!

The translations are continuously improved with every update, so it is part of my Jenkins CI/CD pipeline to regenerate them before deploying to production.
My own translations are kept in separate files to avoid being overwritten.

Fortify is installed, so I get the translations for validation and error messages. However, I use custom Blade views for the authentication forms and wanted to reuse the Jetstream translations for field labels like "remember me", "email", etc.
Since Jetstream is not installed, its translations are not included.

I would like to force certain package translations to be published even if the package is not present, in this case jetstream.

My idea to implement this would be a new configuration option like:

'force_install' => [
"laravel/jetstream",
],

This array could be merged into the list of detected installed packages before translations are generated.