- What does naoray/blueprint-nova-addon do?
- It is a Laravel Blueprint addon that generates Nova resource classes from your draft YAML definitions. It scaffolds fields, relationships, and the resource class itself so Nova admin panels can be built from the same schema source as models and migrations. The goal is to keep Blueprint as the single source of truth during development.
- How do I install naoray/blueprint-nova-addon?
- Install it with Composer, most likely as a dev dependency because it is a code-generation tool rather than runtime code. Run composer require --dev naoray/blueprint-nova-addon and follow the README for any service provider registration or publishable config. Check composer.json constraints first to confirm compatibility with your Laravel and Blueprint versions.
- Is blueprint-nova-addon a dev-only dependency or does it run in production?
- The available evidence suggests it is dev-time tooling that consumes Blueprint YAML and emits Nova resource classes, so it should not be on the request hot path. Confirm this by inspecting its service provider and any runtime hooks before deploying. As a precaution, require it with --dev and exclude it from production installs unless the maintainer documents otherwise.
- Does version 2.0.0 still support Blueprint v1?
- The changelog only states that v2.0.0 added support for Blueprint v2, and a major version bump may mean v1 support was dropped or deprecated. The provided context does not confirm whether v1 remains supported, so check the composer.json constraints and any upgrade guide. Teams still on Blueprint v1 should pin the previous addon release until that is answered.
- Which Laravel and PHP versions are required by blueprint-nova-addon?
- The exact minimum PHP and Laravel versions are not documented in the available release notes. Read the require section of the package composer.json, and check whether the v2.0.0 major bump raised the platform floors. Also verify the laravel/nova constraint because Nova is a commercial package with its own version requirements.
- Can I use blueprint-nova-addon with an existing Laravel Nova admin panel?
- Yes, provided Nova is already installed and you want to generate resource classes from Blueprint drafts. Before adopting it, run the generator against a representative slice of your schema and diff the output against your committed Nova resources. If the diffs are large or noisy, treat adoption as a workflow migration rather than a drop-in install.
- How should I test generated Nova resources before committing?
- Create a throwaway spike branch, install the addon, and generate resources from a representative set of draft YAML files. Diff the generated output against your current resource classes and review every change. Only after the diffs are empty or explainable should you open a time-boxed pull request on a low-traffic service.
- Does blueprint-nova-addon support Laravel Nova 4 or Nova 5?
- Support for specific Nova major versions is not stated in the provided context and must be confirmed from composer.json or the README. Because Nova is a commercial dependency, its constraint is the most important compatibility check after Laravel and Blueprint versions. If the package constrains Nova below your installed version, Composer will fail or resolve an older addon release.
- What are the alternatives to blueprint-nova-addon?
- The direct alternative is generating Nova resources manually with Nova artisan commands or custom stubs. Another option is a different Blueprint addon or a custom generator that targets your team conventions. The addon only adds value if you already use Blueprint drafts as the schema source; if you hand-write models and migrations, it adds toolchain overhead without a clear payoff.
- Is naoray/blueprint-nova-addon actively maintained and safe to adopt?
- The available assessment is based on a single changelog line, so maintenance signals such as release cadence, open issues, CI status, license, and bus factor still need to be checked. Treat adoption as a hypothesis to validate in a spike branch rather than a settled decision. If the repository shows low activity or unanswered compatibility questions, keep the dependency pinned and isolated.