Weave Code
Starter Kits Laravel Package
laravel-lang/starter-kits
Laravel-Lang Starter Kits is a dev-only Composer package that connects Laravel starter kits to Laravel-Lang localization management. Install with composer require laravel-lang/starter-kits --dev, then run php artisan lang:update to manage locales.
Translations for Laravel Starter Kits
Frequently asked questions about Starter Kits
- What is laravel-lang/starter-kits used for?
- It is a dev-only Composer package that provides translations for the UI strings shipped in the official Laravel starter kits, including their auth, settings, and teams screens. It seeds JSON language files into your Laravel app so you can manage starter kit locales through Laravel-Lang. It is not a runtime framework extension and adds no service provider or production code paths.
- How do I install laravel-lang/starter-kits in a Laravel application?
- Install it as a development dependency with composer require laravel-lang/starter-kits --dev. Then run php artisan lang:update to generate or update the starter kit translation files. The README describes this as the complete setup workflow.
- Which Laravel starter kits and variants does this package cover?
- It targets the official Laravel starter kits built with React, Vue, Svelte, and Livewire. The variants include main, teams, workos, and workos-teams, so you should match the package payload to the starter kit variant your app was scaffolded from. Using the wrong variant wastes most of the supplied translations.
- Does php artisan lang:update overwrite my existing lang files?
- The package documentation does not explicitly state whether lang:update overwrites or merges files already present under lang/. The technical evaluation flags this as the key behavioral question because overwriting could destroy custom strings or human-corrected translations. Test it on a branch, diff the generated lang tree, and if needed adopt a generate-once-then-vendor pattern.
- Is laravel-lang/starter-kits a production dependency?
- No, it is intended as a dev-only package installed with require-dev. It has no runtime coupling, no service provider, and no autoloaded production code paths. The output is plain JSON under lang/, which Laravel's translator and locale middleware consume at runtime.
- Which Laravel versions does laravel-lang/starter-kits support?
- The technical evaluation positions it for Laravel 11 and 12 starter kit projects, but the README does not publish a detailed version matrix. Verify the current Composer constraints on Packagist and test the install against your application's Laravel version before adopting it.
- Do I need laravel-lang/starter-kits if I already use laravel-lang/lang?
- They serve different layers: laravel-lang/lang provides framework-level Laravel strings, while starter-kits adds keys for the official starter kit UI screens. If your app was not scaffolded from an official starter kit, this package likely adds little beyond laravel-lang/lang. If you do use a starter kit, check version compatibility and avoid duplicating translation ownership.
- How reliable are the translations in laravel-lang/starter-kits?
- Quality is bimodal by locale because many missing values are filled by automated machine translation PRs, with later human patches for locales such as es, de, pt_BR, zh_CN, ja, ru, and fa. Spot-check the specific locales you ship, especially revenue- or compliance-critical languages. Treat machine-translated entries as a starting point rather than final copy.
- Can I use this package with React, Vue, Svelte, or Livewire starter kits?
- Yes. The package only supplies key/value JSON for the starter kit UI strings, so the frontend framework does not affect its mechanics or build process. The important match is the starter kit variant, such as main, teams, workos, or workos-teams, rather than the JavaScript framework itself.
- What should I check before using laravel-lang/starter-kits in CI or deployment?
- Keep it out of CI steps that build deployable artifacts unless the generated lang files are committed and reviewed. Confirm there are no Composer post-install hooks, because this is a dev dependency that writes files during a developer- or bot-run artisan command. Also verify the release tag and Packagist metadata before locking it, given the package's low adoption signal and static JSON output that you can fork if needed.
Weaver
How can I help you explore Laravel packages today?