Weave Code
Generator Bundle Laravel Package
pugx/generator-bundle
PUGXGeneratorBundle is a Symfony bundle that scaffolds complete CRUD interfaces from Doctrine entities, generating controllers, forms, templates, and routes with pagination, filtering, and customizable templates to speed up admin and backend development.
An enhancement of SensioGeneratorBundle
Frequently asked questions about Generator Bundle
- Can I use pugx/generator-bundle in a Laravel application?
- No. PUGXGeneratorBundle is a Symfony bundle that extends the deprecated SensioGeneratorBundle and depends on Symfony full-stack conventions, Doctrine ORM, and Twig. It cannot be installed or bootstrapped in a Laravel app without effectively running Symfony alongside Laravel, which is not a defensible architecture. For Laravel, use Artisan make:* commands or maintained Laravel CRUD generator packages instead.
- What does PUGXGeneratorBundle actually do?
- It is a developer-time code-generation tool that scaffolds complete CRUD interfaces from Doctrine entities. It generates controllers, forms, Twig templates, and routes with pagination, filtering, and sortable columns to speed up admin and backend development. It does not participate in request handling at runtime; it writes code into your application and then has no further role.
- How do I install and configure pugx/generator-bundle?
- On a legacy Symfony 2 application, it is installed with Composer as a development dependency, registered in AppKernel, and used through its generator commands. Templates can be overridden locally, but every override increases the cost of eventually replacing the tool. It should not be added as a new dependency in any current stack.
- Which Symfony and PHP versions does pugx/generator-bundle support?
- It targets the Symfony 2 era and is built around SensioGeneratorBundle, Doctrine ORM, and Twig versions from that period. There is no PHP 8+ compatibility work and no support for Symfony 4, 5, 6, or 7. Adopting it locks PHP, Symfony, Twig, Doctrine, and SensioGeneratorBundle versions together.
- Is pugx/generator-bundle still maintained?
- No. The repository is archived, has zero dependents, and is a historical artifact rather than an active package. No security advisories will be issued and no fixes for Twig 2 or 3, Doctrine ORM 2.7+, or PHP 8 will land. Archived Composer packages with no maintainer are a common finding in dependency audits.
- What is the modern alternative to PUGXGeneratorBundle?
- For Symfony, the replacement is MakerBundle with make:entity, make:form, and make:crud commands on Symfony 3.4 and later. For Laravel, the equivalents are Artisan generators, the framework's built-in make:* commands, and maintained community CRUD scaffolding packages. The correct move is to replace the scaffolding tool, not to patch an abandoned bundle.
- Does PUGXGeneratorBundle work with Doctrine ORM 2.7+ or Twig 2 and 3?
- There is no guaranteed compatibility with newer Doctrine ORM or Twig releases. The generated code reflects older Twig and Bootstrap-era idioms, so upgrades in any one of PHP, Symfony, Twig, or Doctrine can break scaffolding. This version lock-in cascade is the main technical risk even for legacy Symfony 2 projects.
- Is it safe to use pugx/generator-bundle in production?
- It is a development-time code generator, not a runtime dependency, so it does not execute in production request handling. However, the code it generates becomes production code and inherits its assumptions about Doctrine mappings, Symfony form types, and Twig templates. The bigger production concern is compliance: archived dependencies with no maintainer can block audit sign-off even when runtime risk is zero.
- Can the CRUD generated by PUGXGeneratorBundle be tested?
- The generated controllers, forms, and templates are ordinary Symfony code, so they can be covered by functional and unit tests in the host application. The tool itself is not a testing framework and provides no test generation or test harness. Any tests you write will need to be rewritten or discarded when you migrate to a current scaffolding approach.
- How do I migrate from PUGXGeneratorBundle to Symfony MakerBundle?
- Treat it as a replacement project rather than an integration project. On a legacy Symfony 2 codebase, migrate scaffolding to MakerBundle on a current supported Symfony version and regenerate or hand-port the CRUD screens. If the real requirement is modern CRUD scaffolding for Laravel, choose a maintained Laravel generator instead of standing up Symfony alongside Laravel.
Weaver
How can I help you explore Laravel packages today?