- What does bernhardh/nova-dynamic-views do?
- It is a Laravel Nova package for dynamically overwriting custom placeholders so you can present tailored resource tables without duplicating Nova resource classes for every variation. It is aimed at Nova admin and internal tooling use cases, not public application rendering or API behavior. The package is archived and was last released in 2022, so treat it as a spike or fork candidate rather than a default dependency.
- How do I install bernhardh/nova-dynamic-views?
- Installation is Composer-based inside a Laravel Nova application, typically with composer require bernhardh/nova-dynamic-views, but confirm the exact package name, version constraint, and service-provider behavior in the README and composer.json first. Because the repository is archived, avoid installing it directly into production without a review. Run the install in a disposable Nova app before adopting it.
- Which Laravel, PHP, and Nova versions are supported?
- The package was last released in 2022 and is archived, so its Laravel, PHP, and Nova version constraints must be read from composer.json and the README rather than assumed. It may rely on Nova internals that have changed across major releases. Validate against the exact versions in your application during a time-boxed spike.
- How does the custom placeholder syntax and resolution work?
- The package lets you dynamically overwrite custom placeholders in Nova views, but the exact placeholder syntax and resolution behavior must be confirmed by inspecting the source and README. Determine whether placeholders are resolved at render time, request time, or through caching, because that affects query load and correctness. Profile realistic admin screens before relying on it.
- Does it escape placeholder output and enforce authorization?
- The TPM assessment flags possible XSS or data-leakage risk if dynamic placeholder content is not escaped or authorized correctly. Inspect the rendering path and test with untrusted content and restricted Nova users before enabling the package. Do not assume safe escaping or Nova policy enforcement without verifying it in source.
- Is bernhardh/nova-dynamic-views safe for production use?
- Not by default. The package is archived, has low community signal, and has no vendor support, so production use requires an internal owner, an exact version pin, a security review, automated tests, and a feature flag for isolation. If the behavior is valuable, prefer a small internal reimplementation or a tested fork with explicit constraints.
- Can I use it with current Laravel Nova versions?
- Compatibility with current Nova releases is unknown and should be treated as risky because the last release was in 2022 and Nova internals change across major versions. Run a spike in staging with your exact Nova, Laravel, and PHP versions, and test a Nova upgrade before enabling it broadly. Because the package is archived, assume compatibility will degrade over time unless your team forks it.
- Does the package have tests and documentation?
- Community signal is minimal and the repository is archived, so do not assume strong documentation or test coverage. Inspect the README and source, run any existing tests, and add your own tests around placeholder resolution, escaping, and authorization. Missing tests increase the chance of undocumented edge cases in Nova admin screens.
- What are alternatives to bernhardh/nova-dynamic-views?
- Native Nova custom fields, Nova macros, or a small internal Laravel and Nova implementation can often provide tailored resource tables without duplicating resource classes. Evaluate those first if you need maintained code, explicit authorization, and controlled escaping. A vendored fork is another option only after license, source, dependency, and security review.
- How should I maintain or fork an archived Nova package?
- Fork or vendor it only after auditing the license, source, dependencies, and security behavior, then assign an internal owner. Pin exact versions, isolate usage behind a feature flag, add tests for placeholder rendering and authorization, and document the Nova upgrade and rollback process. Without that ownership and review, the dependency should not be approved for production.