- What is savannabits/web-generator used for?
- It is a Laravel 7 CRUD generator for savannabits/craftable that scaffolds a vertical slice of an admin resource: migration and model, repository, controller, route, Blade/Vue views, Vue components, and sidebar menu registration. It is a development-time scaffolding tool, not a production runtime dependency. It is most useful if your team already standardizes on Laravel with Vue and a repository pattern.
- Which Laravel and PHP versions does savannabits/web-generator support?
- The package is described as a Laravel 7 CRUD generator, but the supplied material does not include a Laravel/PHP version matrix or a stated backward-compatibility policy. Check the composer.json constraints in the exact tag you plan to use before spiking. Pin the version in require-dev and commit the lockfile rather than letting it float.
- How do I install savannabits/web-generator in a Laravel app?
- Install it with Composer as a development dependency, then publish its configuration and stubs and run the generator Artisan command. The exact command signature and publish tags should be taken from the package README for your pinned version. Because generated files become owned source code, run the first install on a throwaway branch and review the output before committing.
- Do I need savannabits/craftable installed to use this generator?
- Yes, the package is described as a CRUD generator for savannabits/craftable, so treat craftable as part of the expected stack. The generator scaffolds resources that fit craftable's admin conventions, including a sidebar menu registration. Verify the compatible craftable version in composer constraints before installing.
- Does savannabits/web-generator support Vue 3, Inertia, or Livewire?
- The available material indicates hard-coded frontend assumptions around Vue and a specific admin layout/sidebar convention, but it does not confirm Vue 2 versus Vue 3 or support for Inertia, Livewire, or React. If your app uses Livewire, Inertia+React, or Blade-only, the frontend half of the generated output is likely dead weight and the backend half will need rework. Inspect the published stubs before assuming partial value.
- Can I customize the stubs and generated templates?
- Yes, stub publishing is the critical customization lever: publish the package stubs into your app and edit them to match house style for validation, authorization, naming, and fillable rules. Without stub customization, adoption often stalls on style mismatches. Treat your customized stubs as the durable internal asset and the package as a convenience wrapper.
- Does the generator create FormRequests, policies, factories, seeders, and tests?
- The material names migration/model, repository, controller, route, Blade/Vue views, Vue components, and sidebar menu registration as the generated layers. It does not evidence FormRequests, policies, factories, seeders, or automated tests. Spike one representative entity and review every artifact against your internal standards before rolling it out.
- Will savannabits/web-generator overwrite my existing files?
- The supplied material does not state whether the generator supports dry-run, force flags, or conflict prompts, so overwrite behavior must be verified for your pinned version. Run it on a clean branch with a committed working tree and inspect the diff. Do not run it against existing modules you are not prepared to review line by line.
- Is savannabits/web-generator safe to use in production?
- It has no production runtime exposure because it is a dev-time scaffolding package; the generated code is inspectable and reviewable before it ships. The main production risk is propagating bad boilerplate, such as weak validation, missing authorization, or unsafe mass-assignment defaults, across many modules. Review generated output for security-relevant defaults and keep the package in require-dev.
- Who maintains savannabits/web-generator, and what changed in v7.0.0?
- The material identifies a small-vendor/bus-factor risk and does not evidence maintainer count, release cadence, issue-response record, or a backward-compatibility policy. v7.0.0 is a major bump, but the supplied release note is marketing copy with no changelog, so the v6.x-to-v7.0.0 upgrade surface is unevidenced. Pin the exact version, review the diff, and confirm the license fits your distribution model.