Weave Code
Nova Locale Manager Laravel Package
optimistdigital/nova-locale-manager
Nova Locale Manager is a Laravel Nova tool for managing your app’s locales from the admin panel. Add, edit, enable, or disable languages and set the default locale without editing config files, simplifying multilingual Nova applications.
An extremely simple Laravel Nova tool for managing locales.
Frequently asked questions about Nova Locale Manager
- How do I install optimistdigital/nova-locale-manager in a Laravel Nova app?
- Install it with Composer using composer require optimistdigital/nova-locale-manager, then register the tool in your NovaServiceProvider's tools() method. Publish and run any migrations the package ships so the locale table exists, then seed your existing locales. Check the package's composer.json for the exact Nova, Laravel, and PHP constraints before installing.
- Does nova-locale-manager handle translations or just locales?
- It only manages locale records such as language codes, enabled/disabled state, and the default locale. It is not a translation management system and does not store translated content, fallback chains, or translation workflows. Keep it as a small admin-side locale registry and use a separate translation package for content.
- Which Laravel, PHP, and Nova versions does nova-locale-manager support?
- The package's composer.json is the source of truth for supported Nova, Laravel, and PHP versions. Its last release was 2022-07-18, so compatibility with current Nova and Laravel majors is the main risk to verify. Pin the version and test against the exact matrix you run in staging before adopting it.
- How do I set the default locale with Nova Locale Manager?
- The tool lets an admin mark one locale as the default from the Nova UI, replacing manual edits to config files. Your application still needs a runtime resolver that reads the default from the database, ideally through a cached service provider. Add a guardrail so the default locale cannot be deleted or disabled accidentally.
- Can admins delete the default locale or create invalid locale codes?
- That depends on the validation and policies included in the package, which you should confirm before production use. Test destructive actions explicitly and add a default-locale lock plus locale-code validation if they are missing. Since the scope is small and MIT-licensed, patching or forking these guardrails is straightforward.
- How do I migrate existing config-based locales into the locale table?
- Inventory your current locale source of truth first, then define the schema, validation rules, and default-locale behavior. Publish and run the migration, seed the existing locales, and update your locale resolver to read from the table with caching and a fallback. Verify the resolved locales match the old config before retiring the file-based list.
- Is nova-locale-manager still maintained, and what are the alternatives?
- The package has a small footprint, around 16 stars, a single-vendor origin, and a last release in July 2022, so treat active maintenance as unlikely. Lock-in is low because the scope is simple and MIT-licensed, so you can fork it or replace it with a small in-house Nova resource. Alternatives include keeping locales config-driven or building a minimal CRUD tool yourself.
- Does nova-locale-manager support multi-tenant or per-tenant locales?
- There is no indication that per-tenant locale scoping is supported, and it likely exceeds the package's deliberately simple scope. If you need tenant-specific locale catalogs, plan on extending the schema and queries yourself. For single-tenant apps needing admin-managed locales, the default behavior is usually sufficient.
- How do I make my Laravel app use the locales stored by this tool?
- Wire your locale middleware or service provider to read enabled locales from the package's table, defaulting to the marked default locale. Cache the resolved list and invalidate that cache whenever an admin changes a locale. This keeps runtime locale resolution decoupled from the Nova admin tool.
- What should I check before using nova-locale-manager in production?
- Run the migration on a staging clone, verify Nova tool registration, authorization policies, views, and assets, and confirm cache behavior works as expected. Pin the package version, run Composer audit, and roll out behind a feature flag with a documented rollback. Also decide who owns a fork if upstream is abandoned.
Weaver
How can I help you explore Laravel packages today?