- What does norman-huth/nova-assets-changer do for Laravel Nova?
- It is a Laravel Nova package that overlays replacement CSS and JavaScript onto the assets Nova serves, by swapping or branding files under vendor/laravel/nova/public. It is meant for presentation-layer customization without forking Nova or editing vendor files by hand. It is not a Nova capability or admin-surface replacement; treat it as a deploy-time patch.
- How do I install and configure nova-assets-changer in Laravel?
- Install with Composer using the registry name norman-huth/nova-assets-changer, pin 1.2.4, then run vendor:publish and the package's artisan step as described by the package. Before installing, resolve the identity mismatch between the norman-huth registry name and the Muetze42 repository and Composer namespace so you know you are installing the audited code. A Laravel-fluent engineer can usually spike this in under a day.
- Which Laravel Nova versions does nova-assets-changer support?
- Version 1.2.4 exists specifically as a Nova 5 fix, so it is the release to evaluate for Nova 5. It is unknown whether that fix preserves Nova 4 behavior, and the package may now be Nova-5-only. Check the declared laravel/nova constraint in Composer before adopting it, especially if you still run Nova 4.
- Is nova-assets-changer still maintained, and what are the alternatives?
- No. The package is archived and has a single maintainer, so it is no longer receiving upstream fixes. For existing installs that means you own it now; for new adoption it is close to disqualifying. The realistic alternatives are to fork and maintain it internally, vendor the code you audited, or use the archive as a time-buying bridge while planning your own admin surface.
- Why does the Composer name differ from the repository namespace?
- The registry entry is norman-huth/nova-assets-changer, while the repository and Composer namespace references use Muetze42. That supply-chain identity mismatch must be resolved before anything merges into a production branch. Confirm you are installing and auditing the same code, and account for the non-contiguous changelog from 1.2.2 to 1.2.4 with 1.2.3 unaccounted for.
- Can I change Nova's CSS and JavaScript without editing vendor files?
- Yes, that is the package's purpose: it is a config-driven asset overlay that swaps or brands Nova's shipped CSS and JavaScript under vendor/laravel/nova/public. You avoid hand-editing vendor files, but the tool still mutates assets the admin panel cannot boot without. Because the blast radius is small but severe, own it as build and deploy tooling with a named owner rather than silently absorbing it as application code.
- How should I handle testing and CI when Nova requires a license?
- Automated verification requires a licensed Nova install in the CI pipeline because Nova is a paid, credentialed dependency. There are no field reports to lean on and no known test path that runs without a Nova license. If you cannot test the asset changes in CI, the safest decision is not to ship them.
- Does it work with containerized deployments or gitignored public/vendor?
- This has not been validated for immutable or containerized deployments where public/vendor is gitignored. Because it rewrites Nova's published assets, run it at build or deploy time after Nova assets exist, then bake the result into the image or a persistent layer. Verify the behavior in your actual pipeline before relying on it.
- Should I pin version 1.2.4 instead of using ^1.2?
- Pin exactly 1.2.4 and never use a caret range such as ^1.2. The changelog jumps from 1.2.2 to 1.2.4 with 1.2.3 unaccounted for, and a caret range is exactly where a silent move across a Nova major could happen. Treat the exact pin as a planning and review requirement, not just an engineering preference.
- What happens if I run it twice or after nova:publish?
- Idempotency and drift are unvalidated for this package. Asset-rewriting tools are sensitive to repeated runs, and nova:publish or nova:install can overwrite your customizations. Test a second consecutive run and a full Nova publish cycle in staging before using it on a production panel.