Weave Code
Generator Builder Laravel Package
infyomlabs/generator-builder
InfyOm Generator Builder adds a visual web interface to Laravel's InfyOm Generator, letting you define models, fields, and relationships, then generate CRUD controllers, views, routes, and migrations without writing boilerplate by hand.
InfyOm Laravel Generator GUI Builder
Frequently asked questions about Generator Builder
- What is infyomlabs/generator-builder used for?
- It is a web GUI wrapper around the InfyOm Laravel Generator. Instead of running artisan commands, you define models, fields, and relationships in a browser form, then generate CRUD controllers, Blade views, routes, and migrations. It is a development-time scaffolding tool, not a runtime dependency, so the generated PHP and Blade files have no ongoing coupling back to the package.
- How do I install infyomlabs/generator-builder in a Laravel app?
- Install it with Composer as a dev dependency and pull in the sibling infyomlabs/laravel-generator package it builds on. You need publishable assets and routes, plus filesystem write access to app/, database/, routes/, and resources/views/ at generation time. Check the repository README for the exact vendor:publish tags and route registration steps, since these are not covered by a changelog. In containerized or read-only-filesystem setups, plan for that write access up front.
- Does Generator Builder support Laravel 10, 11, or 12?
- That is not verified. The last release is dated 2022-02-22 with a single v1.0.0 tag and no changelog beyond "First Tagged Release," which places it in the Laravel 9 era. Read the actual composer.json illuminate/* constraints and the CI workflow to see which versions are exercised rather than assuming compatibility. If your app is on a newer Laravel major, expect to test generation end to end before committing to it.
- Is it safe to leave infyomlabs/generator-builder enabled in production?
- No. The package exposes a browser UI that writes executable PHP files to disk, so a reachable route is effectively a remote-code-generation surface. It should never appear in a production composer.json, and any staging instance needs environment gating, authentication, and ideally IP restriction. Treat a misconfiguration as a persistence and exfiltration vector, not a cosmetic bug.
- Can I override the Blade and repository templates to match my own conventions?
- Template override is the make-or-break question for this package, and it depends on whether the host app can publish and swap the stub files or whether you must fork the generator. Generated code is idiomatic-ish Laravel, but that is not the same as matching your house patterns for authorization, validation layering, and error handling. Confirm override support before adoption, otherwise budget for a fork you will have to maintain yourself.
- What happens to my hand-edited files when I regenerate a CRUD module?
- Manage, regenerate, and rollback are marketed features, but in practice regeneration can overwrite or delete files you have edited by hand. The undo story is your filesystem or version control, not the tool itself. Before using it on an existing module, confirm whether regeneration is idempotent and whether it diffs or blindly overwrites, and never run it against uncommitted work.
- Does infyomlabs/generator-builder require infyomlabs/laravel-generator at runtime?
- It depends on the sibling infyomlabs/laravel-generator package, but the important distinction is whether that dependency is needed only during generation or at request time. Since both are code-authoring tools, neither belongs in a production dependency graph. Verify the composer.json require versus require-dev split so the generator stack does not leak into your deployed runtime.
- How do I secure the Generator Builder routes?
- Wrap the published routes in auth middleware at minimum, restrict access to local or known IPs, and register them only in local and staging environments. Because the UI writes executable PHP, an unauthenticated route is a code execution path. Review the generated route file after publishing rather than assuming the package ships with safe defaults.
- Does Generator Builder generate tests, API resources, or form requests?
- Form requests and repository classes are part of the InfyOm pattern, but test generation is likely absent and API Resource output is not what this stack targets. The templates are opinionated toward controllers that talk to repositories with Blade views. If your codebase uses invokable actions, DTOs, or API-only responses, expect to rewrite a significant share of the output.
- Is infyomlabs/generator-builder still maintained, and what should I use instead?
- Community signal is low: roughly 132 GitHub stars, a single tag from 2022, and no vendor support path, which implies a bus factor of one or two. Check recent commits and issue response times before depending on it. Alternatives worth evaluating include maintaining your own stubs with artisan make commands, or generator packages with active release cadence, since scaffolding is one area where a small in-house template set often beats an unmaintained dependency.
Weaver
How can I help you explore Laravel packages today?