- What does klepak/nova-dynamic-page-title do?
- It is a Laravel Nova package that updates the browser document title from Nova's Vue Router state. The goal is to make admin tabs and page headings reflect the current resource or screen instead of a static Nova title. It is a presentation-only admin UI enhancement and does not affect domain logic or APIs.
- Is klepak/nova-dynamic-page-title compatible with Laravel Nova 4?
- Compatibility with Nova 4 is not guaranteed. The last release was in December 2020 and the package depends on Nova's internal SPA and Vue Router behavior. Validate it in a staging Nova instance on your exact Nova major version before adopting it.
- How do I install klepak/nova-dynamic-page-title?
- The typical path is to require the package with Composer and confirm that its service provider and assets are registered in your Nova application. Check whether Composer auto-discovery works for your Laravel and Nova versions rather than assuming it does. Then verify title updates on initial load and route transitions in a non-production environment.
- Does this package support Laravel 9, 10, 11, and PHP 8?
- The package's composer.json constraints are the authoritative source, and the 2020 release date makes modern Laravel and PHP support uncertain. Do not assume support from the package description alone. Run a time-boxed compatibility spike against your exact Laravel, PHP, and Nova versions.
- How does it update the browser tab title in Laravel Nova?
- It reads Nova's Vue Router state and updates document.title as routes change. That integration likely touches Nova's internal frontend behavior, which is an undocumented surface. Confirm whether it uses supported extension points or private APIs before relying on it.
- Can I customize Nova page titles for specific resources or screens?
- The package is intended to support dynamic titles per resource or screen, but the exact configuration depends on its implementation and any published config. Test create, edit, detail, index, and error routes, including async record names. If the behavior is incomplete, a small in-house Nova asset may be safer.
- Is klepak/nova-dynamic-page-title actively maintained?
- There is no evidence of active maintenance. The last release was 2020-12-04, adoption is very low, and the repository has few stars. Treat the package as a reference implementation or plan to fork it if you need long-term ownership.
- Does it work with Nova's Vite or Mix asset pipeline and CSP settings?
- That must be verified for your Nova version and asset build. The package may ship precompiled assets that assume an older Nova frontend, and strict Content Security Policy settings can affect injected scripts. Test in staging with your actual CSP and asset pipeline before production.
- What are alternatives if the package is incompatible?
- You can fork it, inline a minimal listener that updates document.title from Nova route and record data, or build a small custom Nova asset or tool. The feature is small enough that an in-house implementation is often lower risk. Keep the fallback small and owned by your application team.
- Is it safe to use in production?
- Security risk is low in scope, but this is an abandoned admin dependency that still needs ownership. Pin the exact release, run a staging compatibility spike, and document a replacement path before rollout. Also add regression checks for title updates on initial load and route changes.