Weave Code
Fixtures Bundle Laravel Package
kunstmaan/fixtures-bundle
KunstmaanFixturesBundle adds flexible fixture loading to Symfony apps, letting you define test and demo data in YAML and load it via console commands, with support for ordering, dependencies, and clean database seeding.
[READ-ONLY] Subtree split of the Kunstmaan FixturesBundle -- master at Kunstmaan/KunstmaanBundlesCMS
Frequently asked questions about Fixtures Bundle
- Is kunstmaan/fixtures-bundle compatible with Laravel?
- No. It is a Symfony bundle built around Symfony's Bundle class, dependency-injection container compilation, YAML service configuration, and Doctrine. Laravel has no Symfony bundle registration mechanism and does not natively bind Doctrine's entity manager, so this is not a drop-in package for a Laravel application. For Laravel, use seeders and factories, or adopt a framework-agnostic fixture parser such as nelmio/alice with a thin Artisan wrapper.
- How do I install kunstmaan/fixtures-bundle?
- It is installed as a Composer package and registered as a Symfony bundle in a Symfony application's kernel. You then configure its services through Symfony YAML configuration and use its console commands to load fixtures. This installation model does not map cleanly to Laravel's package discovery or Artisan command system.
- Does this package support Laravel 10 or Laravel 11?
- There is no Laravel version support described for this package. It targets Symfony 4/5-era conventions and Doctrine, not Laravel 10 or 11. Making it work would require booting or shimming a Symfony kernel and container, pulling in Doctrine, and reimplementing its console command behavior inside Artisan.
- Can I use kunstmaan/fixtures-bundle with Eloquent models?
- No, there is no native Eloquent support. The bundle expects Doctrine's entity manager and Symfony service wiring, so using it with Eloquent would require a bridging layer or running Doctrine alongside Eloquent. That creates two ORMs, two migration stories, and two identity-map models, which is significant long-term maintenance drag.
- What is the best alternative for YAML fixtures in Laravel?
- For most Laravel teams, the correct default is Laravel seeders plus model factories because they are zero-dependency and native to the framework. If YAML authoring is a hard requirement, use nelmio/alice, which is framework-agnostic and actively maintained, and write a small Artisan command that maps Alice objects into Eloquent models. This preserves the YAML-in, fixtures-out workflow without importing a Symfony bundle or a second ORM.
- How does fixture loading work in KunstmaanFixturesBundle?
- The bundle lets you define test and demo data in YAML and load it through Symfony console commands. It supports ordering, dependencies, and clean database seeding. In a Laravel context, those console command semantics would need to be reimplemented inside Artisan because the bundle expects Symfony's Command base class and console I/O helpers.
- Is kunstmaan/fixtures-bundle maintained or abandoned?
- The objective signals are very weak: 1 star, 0 dependents, and an overall score of 0.135. Kunstmaan CMS bundle activity has been declining, and a fixtures helper with zero dependents is a high abandonment risk. If you use it at all, assume a fork-and-own maintenance model rather than relying on upstream fixes.
- Can I use this bundle for production demo data seeding?
- It is intended for fixture loading of test and demo data, including clean database seeding, but it is not a good fit for a Laravel production seeding workflow. Depending on it pulls in a Kunstmaan/Symfony/Doctrine dependency tree that is much larger than the problem being solved. For Laravel production or demo data, prefer Laravel seeders and factories with explicit environment guards.
- Does kunstmaan/fixtures-bundle require Doctrine?
- Yes, the bundle is structured around Symfony/Doctrine conventions and expects Doctrine entity manager binding. That is a central reason it does not fit a Laravel stack where Eloquent is the persistence layer. Adding Doctrine alongside Eloquent just to load fixtures is not a durable integration strategy.
- How do I decide between Laravel seeders and YAML fixtures?
- First clarify whether the real requirement is Laravel seeders or YAML-authored fixtures. If it is Laravel seeders, this package is a non-starter. If it is YAML authoring for ergonomics or diff-friendly fixtures in version control, use nelmio/alice as the parser and a thin Artisan wrapper for Eloquent, rather than adopting a Symfony bundle.
Weaver
How can I help you explore Laravel packages today?