Weave Code
Maker Bundle Laravel Package
survos/maker-bundle
Survos Maker Bundle extends Symfony MakerBundle with generators and scaffolding helpers for rapid CRUD, entity, and admin code creation. It streamlines repetitive setup tasks so you can bootstrap features faster in Symfony applications, with sensible defaults and reusable maker commands.
survos/maker-bundle extends Symfony's MakerBundle with additional generators for rapid scaffolding. It provides custom make: commands to bootstrap entities, CRUD screens, and configuration for Survos-based applications, reducing repetitive boilerplate.
- Extra
make:commands for common Survos patterns - Faster scaffolding of CRUD and admin interfaces
- Consistent generated code and configuration
- Seamless integration with Symfony MakerBundle
- Speeds up prototyping in Symfony projects
Frequently asked questions about Maker Bundle
- Is survos/maker-bundle a Laravel package?
- No. survos/maker-bundle is a Symfony MakerBundle extension that generates admin controllers, Twig templates, and bundle/entity boilerplate using Symfony conventions. It has no Laravel service provider, no Artisan commands, and no Blade support, so it cannot be installed into a Laravel application as-is. Laravel developers should use Laravel-native scaffolding such as Filament, Nova, Backpack, or custom Artisan generators.
- What does survos/maker-bundle actually generate?
- It adds custom maker commands that scaffold Survos-style bundles, entities, admin controllers, and configuration. The output is Twig-based admin screens and Symfony code that you then own and maintain as first-party code. Because the generated files are committed into your project, the real long-term cost is reviewing and standardizing that output rather than the package itself.
- How do I install survos/maker-bundle?
- You would install it with Composer as a development-only dependency in a Symfony project, typically alongside symfony/maker-bundle and Twig. Before installing, verify the composer.json constraints against your exact PHP, Symfony, and Twig versions, since the package has not seen a release since mid-2022. Run it in an isolated branch or sandbox project first, since the generators write files directly into your source tree.
- Which Symfony, PHP, and Twig versions are supported?
- The bundle targets Symfony with Twig and MakerBundle, but its Composer constraints have not been updated since the last release in June 2022. That means modern Symfony and PHP releases are likely to fall outside the declared ranges or hit deprecated APIs. Always read the composer.json and test against your exact target framework version before committing to it.
- Is survos/maker-bundle still maintained?
- Effectively no. It has roughly 4 GitHub stars, zero dependents, and no release since 2022-06-18, which signals very low adoption and little community pressure to fix compatibility issues. There is no vendor SLA or commercial support, so support is limited to GitHub issues and maintainer availability. Any long-term use implies internal ownership of both the generated code and possibly the bundle itself.
- Can I use survos/maker-bundle in production?
- It is a development-time scaffolding tool, so it should never ship as a runtime dependency in production. The generated controllers and templates will run in production, but they become your code and must be reviewed for authorization gaps, template inheritance issues, and adherence to your project standards. Isolate it as a dev dependency and strongly consider removing it once scaffolding is complete.
- What Laravel alternatives should I use for admin scaffolding instead?
- For Laravel, evaluate Filament, Laravel Nova, Backpack, or hand-written Artisan generators that match your team's conventions. These are Laravel-native, actively maintained, and integrate with Eloquent, Blade, policies, and middleware out of the box. Porting survos/maker-bundle to Laravel is not feasible without effectively rewriting it.
- How do I test or validate code generated by survos/maker-bundle?
- Run a sandbox proof of concept in an isolated branch, generate representative admin CRUD screens, and review the output line by line. Then run static analysis, your test suite, and a security review of the generated controllers before merging. Compare the output against your existing admin patterns and native generators to decide whether the conventions actually fit.
- Is it safe to fork or vendor survos/maker-bundle?
- Forking is reasonable if you genuinely need ongoing generation, since the upstream project shows little activity and upgrades may otherwise block you. Check the license first to confirm fork and redistribution terms are acceptable for your organization. If you do fork, document the divergence and add upgrade checks so you are not silently stuck on stale templates.
- What are the main risks of adopting survos/maker-bundle?
- The biggest risks are version incompatibility with current Symfony and PHP releases, stale generator templates, and hidden coupling to Survos conventions that may not match your project. Generated code can also diverge from your team's standards or introduce admin authorization gaps if not reviewed. Combined with dependency abandonment, these risks are high enough that a spike-and-review process is essential before any adoption decision.
Weaver
How can I help you explore Laravel packages today?