- What does cloudstudio/resource-generator do?
- It is a build-time scaffolding utility for Laravel that introspects your database schema and generates PHP classes, including Nova resource classes, from your Eloquent models. The goal is to remove repetitive API and admin scaffolding so you can edit generated code instead of writing it from scratch. It is not a runtime dependency: there is no service provider, middleware, or request-time configuration to keep in production. The durable output is ordinary PHP that you own.
- Does cloudstudio/resource-generator support Laravel 10, Laravel 11, and current Nova versions?
- The package's last release is dated 2022-03-12, which predates Laravel 10, Laravel 11, and later Nova field APIs. Composer constraint resolution against a current Laravel and Nova stack is the first gate and should fail loudly rather than degrade silently. Test in a scratch or staging environment before assuming compatibility. Because Nova is paid and closed-source with its own release cadence, verify the exact Nova version you run.
- Should I install cloudstudio/resource-generator in require or require-dev?
- It is a build-time generator, not a runtime dependency, so require-dev is the appropriate placement. You run it once per domain, review and commit the generated PHP, and can remove the package afterward. There is no service provider to keep registered and no schema change or queue worker involved. This keeps blast radius confined to the generation session.
- Does it generate only Nova resources, or also Eloquent models, controllers, requests, and routes?
- The technical assessment says it introspects the schema and emits Eloquent models, controllers, requests, routes, and/or Nova resource classes, while the repository tagline describes Nova-specific resource scaffolding. Those are different scopes with different prerequisites. Read the command surface from source rather than trusting the README alone. Confirm which artifacts your target version actually emits before scoping a pilot.
- Can I generate resources into a scratch namespace or path and diff before touching app/Nova?
- That is the recommended integration path: use a scratch or dev environment with a staging schema snapshot, generate, review, and commit. Targeting a scratch namespace or path lets you diff generated output before it touches app/Nova, though you should verify the package exposes configurable namespaces or paths in source. The assessment notes the description mentions configurable namespaces, but the command surface should be confirmed. Treat generation as a deliberate, diff-reviewed operation.
- What happens if I re-run the generator over Nova resources I have already hand-edited?
- Regeneration drift is a known risk: re-running over hand-tuned resources may overwrite manual edits. Treat regeneration as a deliberate, diff-reviewed, one-way operation, never a routine command. It is unclear from the available notes whether behavior is idempotent, additive, or overwriting, so verify against a throwaway branch. Keep generated resources under version control so diffs reveal any overwrite.
- Which database schema features are likely to break generated resources?
- Schema-driven generation infers field types and relationships from column types and foreign keys, so predictable failure points include polymorphic relations, pivot tables, enums, JSON columns, custom casts, and non-standard primary keys. Generated resources can load cleanly and still render wrong or throw at query time, which is a quiet and expensive failure. Test against your largest and most irregular tables, not just a simple model. Review relationship metadata manually.
- Does it generate Nova policies, filters, lenses, actions, and relationship metadata?
- The available notes do not confirm the full artifact list; the repository tagline emphasizes Nova resource classes, while the broader description mentions models, controllers, requests, and routes. Whether policies, filters, lenses, actions, and relationship metadata are emitted should be determined from source and a test run. Do not assume coverage beyond fields and relationships. Scope the pilot around exactly what you need to scaffold.
- Is cloudstudio/resource-generator maintained and safe to use in production?
- The default assumption should be unmaintained: no release since 2022-03-12, roughly 105 stars, zero dependents, and a single-maintainer signal. That does not prove poor quality, but it means no community backstop and no guarantee of fixes for newer Laravel or Nova APIs. Safety comes from using it as a one-off, require-dev generator whose output you own and review. It is not a runtime production dependency.
- What should I use instead if the package is stale or my stack is not Nova?
- If your admin surface is Filament, a custom Blade console, or a separate SPA, this package is irrelevant and you should spend no evaluation budget. If you use Nova but the package fails Composer resolution, generate resources manually or with a maintained internal generator, since the durable artifact is ordinary PHP. The decision is reversible and lock-in is effectively zero. Establish a baseline of hours spent per resource so you can tell whether any pilot paid off.