Commit

7318e3e

Sharing Laravel Lang translations straight into React through Inertia without maintaining two separate i18n JSON trees on the backend and frontend is a super clean starter kit setup.
Thanks! That's exactly the idea — keeping translations on the Laravel side and sharing them with React through Inertia, without maintaining separate translation trees. One small detail: some strings aren't covered by the upstream https://github.com/Laravel-Lang/starter-kits translations, so I maintain those additions and overrides in lang/vendor-patches/. A composer patch-vendor step merges them into Laravel Lang before lang:update generates the final translation files. I've also documented this workflow in .ai/rules/ so coding agents follow the same conventions.
GitHubGitHub - Laravel-Lang/starter-kits: Translations for Laravel Starter KitsTranslations for Laravel Starter Kits. Contribute to Laravel-Lang/starter-kits development by creating an account on GitHub.

commit 7318e3e