Weave Code
Nova Targomaan Laravel Package
armincms/nova-targomaan
ArminCMS Nova Targomaan is a Laravel Nova tool for translation management, helping teams edit, organize, and maintain multilingual language strings directly from the Nova admin panel.
Nova Targomaan
Frequently asked questions about Nova Targomaan
- What is armincms/nova-targomaan used for?
- It is a Laravel Nova tool for translation management, letting teams edit, organize, and maintain multilingual language strings from inside the Nova admin panel. Because it is a Nova add-on, it registers into the Nova UI rather than working as a standalone package. The practical appeal is editing translations without leaving the admin area your team already uses.
- Does nova-targomaan support Laravel Nova 3?
- The only release line evidenced is v2.0.0, labelled Upgrade to nova 4, which strongly suggests the package now targets Nova 4 and has dropped Nova 3. The note does not explicitly confirm that Nova 3 support was removed, and no maintained 1.x line is documented in the available material. Treat Nova 3 compatibility as unconfirmed until you check the composer.json constraints or ask the maintainer directly.
- How do I install armincms/nova-targomaan in a Laravel application?
- Install it with Composer, typically composer require armincms/nova-targomaan, from an application that already runs Laravel Nova 4. Nova tools commonly also require publishing config or assets and registering the tool in your NovaServiceProvider, but the exact steps are not documented in the material available here. Verify the service provider registration and any publish commands against the repository before rolling it out.
- What are the PHP and Laravel version requirements for nova-targomaan?
- They are not documented in the release information available, so inspect the package composer.json for its laravel/framework, laravel/nova, and php constraints after requiring it. Nova 4 imposes its own PHP and Laravel floors, and this package's constraints may be stricter than your host application's. Do not assume the package supports the same version matrix as your app.
- Is there a migration guide from version 1.x to 2.0.0?
- No migration guide or changelog beyond the single line Upgrade to nova 4 appears in the available evidence. A major version bump without documentation means you cannot plan against renamed config keys, changed view namespaces, altered tool registration, or rebuilt front-end assets. Diff the published config and assets between versions, or ask the maintainer, before upgrading an existing installation.
- Is nova-targomaan safe to use in production?
- Technically the integration risk is low if your application already runs Laravel Nova 4, since the package is a native Nova add-on with a narrow footprint. The bigger concerns are project-level: no changelog, an undocumented support matrix, and an unverified test and CI posture. Pin the version in composer.json and smoke-test translation editing in staging before relying on it in production.
- Do I need a paid Laravel Nova license to use this package?
- Yes, indirectly. Laravel Nova is a commercial, closed-source package licensed per site, and Nova Targomaan is an add-on that runs inside Nova, so it cannot be used without a licensed Nova installation. That also means your risk surface includes Nova's own release cycle, not just this package's. Budget for Nova licensing alongside the package itself.
- How does nova-targomaan compare to laravel-translation-manager or spatie/laravel-translation-loader?
- Those are framework-level packages that work in any Laravel application, while Nova Targomaan is tied to the Nova admin panel and only makes sense if Nova is already part of your stack. The trade-off is convenience inside an interface your team already knows versus coupling to a commercial dependency. If you do not run Nova, a non-Nova translation manager is the more sensible choice.
- Is nova-targomaan actively maintained, and what is the bus factor?
- Only a single release line is evidenced, so release cadence, issue responsiveness, and contributor count could not be verified. Nova ecosystem packages are frequently single-maintainer projects, which raises the bus factor and makes pinned versions and a local fork prudent. Check the repository commit history, open issues, and recent releases before adopting.
- Is nova-targomaan tested against multiple Nova 4 minor versions?
- There is no indication in the available material of automated coverage across multiple Nova 4 minor releases. Nova 4 reworked tool bootstrapping and moved its front end to Vue 3, so packages coupled to those internals can break on Nova minor upgrades. Plan your own regression check of translation editing after each Nova update.
Weaver
How can I help you explore Laravel packages today?