radermacher/nova-current-environment-card
A Laravel Nova card that displays your application's current environment directly on the dashboard, so you can instantly confirm whether you're working in local, staging, or production. Simple to install and configure, it helps prevent costly mistakes.
Architecture fit: The release note references Nova::translations, which strongly indicates this is a Laravel Nova extension (tool, card, field, or resource package) rather than a general Laravel package. It therefore inherits Nova's package conventions: a service provider, config publishing, asset compilation, and Nova's localization pipeline. For teams already standardized on Nova, this fits cleanly. For teams on Filament, Inertia-only admin panels, or plain Blade, the package is not applicable.
Integration feasibility: Low-to-moderate friction. The 2.0.0 change adds language files and switches string resolution to Nova::translations, which is the idiomatic Nova approach. This means the package no longer needs to maintain a custom translation loader and will follow the host application's locale automatically. Feasibility depends on the Nova major version pinned by the consuming app — Nova::translations requires a Nova release that exposes that API, so Nova 4.x+ should be assumed unless confirmed otherwise.
Technical risk: The major version bump (1.x → 2.0.0) is the primary risk signal. Even though the functional change is additive (new language files), the version number implies a compatibility break with the prior line — most likely a minimum Nova/PHP/Laravel version raise, or removal of a previously public translation/config surface. Without a changelog diff against 1.x, the breakage scope is unquantified. Secondary risk: translation keys moved into package-provided language files can silently change published-string overrides that consumers had customized.
Key questions:
package::file.key), and do they collide with any strings consumers previously overrode via lang/vendor/?Nova::translations?Stack fit: Suitable for Laravel + Nova applications. The Nova::translations usage is a positive signal — it means the package defers to Nova's localization service provider, so locale switching via Nova's user preference or app()->setLocale() will propagate without extra wiring. Confirm the package registers its translations in boot() with loadTranslationsFrom and that we are not required to publish language files to make them work.
Migration path: Because this is a major bump, treat it as a planned upgrade rather than a routine composer update. Steps: (1) pin the current 1.x version in composer.json so an incidental update does not pull 2.0.0; (2) read the 1.x → 2.0.0 diff for removed config keys and published assets; (3) upgrade in a branch, clear bootstrap/cache and view:clear, and re-publish any vendor assets; (4) verify our existing lang/vendor/{package} overrides still resolve — this is the highest-probability regression.
Compatibility: Two axes to check before committing: Nova major version and PHP version. If our Nova install is older than the floor for Nova::translations, the upgrade is blocked until Nova itself is upgraded, which turns a small package bump into an admin-panel upgrade project. Also verify the package has no dependency on novapackages/… transitive helpers that may themselves have version constraints.
Sequencing: Do this as an isolated, single-package change with no other dependencies in flight. If a Nova upgrade is required, sequence Nova first, verify the admin panel is stable, then upgrade this package. Localization work (reviewing shipped locales, submitting missing ones) can follow the code upgrade rather than block it.
Maintenance: Low ongoing burden. Pulling strings into Nova's translation service is a maintenance simplification — the package author no longer hand-rolls a locale loader, and we get upstream locale support for free. The trade-off: we inherit whatever locales the maintainer ships, and adding a locale means an upstream contribution rather than a local override.
Support: Support surface is narrow and mostly self-inflicted: our own custom translation overrides and any published config. Recommend documenting, in our internal runbook, which strings we override and why, so a future package bump does not silently revert them.
Scaling: Negligible runtime impact. Translation file loading is a boot-time concern, cached in production by Laravel's config and translation caching. No scaling considerations beyond standard php artisan optimize in deploy.
Failure modes: Three realistic ones. (1) Silent string regression — after upgrade, a locale falls back to en because our lang/vendor overrides key off the old namespace. Detect with a post-deploy visual check of a non-English admin locale. (2) Missing-translation keys rendering as raw package::file.key strings in the UI — cosmetic but visible and trust-damaging for non-English users. Detect with a smoke test across each supported locale. (3) Hard failure at boot if the installed Nova version lacks Nova::translations — this surfaces immediately as an admin panel 500 and is caught in staging, not production, if we stage the upgrade.
Ramp-up: Minimal. Any Laravel developer familiar with lang/ and lang/vendor/ publishing understands the model. The only learning is Nova's locale-resolution order and how it interacts with per-user locale preferences — worth a short note in the PR description so reviewers know where to look if a translation regresses.
How can I help you explore Laravel packages today?