Wrong Lang directory for Laravel 11

[stefanrakicfaxi]

In your LaravelJsLocalizationServiceProvider you have conditions:
if ($laravelMajorVersion === 4) {
$langs = $app['path.base'].'/app/lang';
} elseif ($laravelMajorVersion >= 5 && $laravelMajorVersion < 9) {
$langs = $app['path.base'].'/resources/lang';
} elseif ($laravelMajorVersion >= 9) {
$langs = $app['path.base'].'/lang';
}

I use Laravel 11 and $laravelMajorVersion = 11, and when you are in this elseif ($laravelMajorVersion >= 5 && $laravelMajorVersion < 9) condition is true and try to read from wrong directory, please add condition >= 5 && < 9

[jonaszkadziela]

@stefanrakicfaxi I am facing the same problem in my Laravel 11 project. As a temporary solution, you can overwrite the service provider.

Create app/Providers/LaravelJsLocalizationServiceProvider.php with the following content:

<?php

namespace App\Providers;

use Mariuzzo\LaravelJsLocalization\Commands\LangJsCommand;
use Mariuzzo\LaravelJsLocalization\Generators\LangJsGenerator;
use Mariuzzo\LaravelJsLocalization\LaravelJsLocalizationServiceProvider as BaseLaravelJsLocalizationServiceProvider;

class LaravelJsLocalizationServiceProvider extends BaseLaravelJsLocalizationServiceProvider
{
    /**
     * There is a problem in v1.11.1 of mariuzzo/laravel-js-localization package.
     * So, we overwrite the register method to use the correct path for language files.
     */
    public function register(): void
    {
        $this->app->singleton('localization.js', function () {
            $files = $this->app['files'];
            $langs = $this->app['path.base'] . '/lang';

            $messages = $this->app['config']->get('localization-js.messages');
            $generator = new LangJsGenerator($files, $langs, $messages);

            return new LangJsCommand($generator);
        });

        $this->commands('localization.js');
    }
}

And register it in bootstrap/providers.php:

<?php

return [
    App\Providers\AppServiceProvider::class,
    App\Providers\LaravelJsLocalizationServiceProvider::class,
];

[bhanwarpsrathore]

@stefanrakicfaxi @jonaszkadziela This is fixed in #192

[fsasvari]

This is merged, but...

I don't see the new tag version 1.11.2 or something, so I cannot pull it to my project...

Can you pls tag it as a new release?

[paulomfr]

Hi @fsasvari

Because it wasn't release yet, I changed to get the package from the master branch on my composer.json. Just change from the package version to 'dev-master'. When it release, we can put the version again.

[fsasvari]

@paulomfr any idea when that is gonna be?

Because, I really don't like the dev-master usage on the production 😬

[paulomfr]

@fsasvari no idea. I just found this package to work on my application and had this issue.

Maybe you can fork this project and release it and then install using git URL?

[bhanwarpsrathore]

I am in talks with the author on email, will get it released in a day or two. He is been very sick past few days.

[bhanwarpsrathore]

@fsasvari @paulomfr A new tag has been released

[IP-Developer]

You can fix this by specifying the source directory when running the command: --source=resources/lang