Weave Code
Fixture Bundle Laravel Package
funddy/fixture-bundle
Funddy Fixture Bundle provides fixture loading and management utilities for PHP/Symfony applications, helping you seed databases with sample or test data during development and testing while keeping fixture definitions organized and reusable.
Fixtures bundle for Funddy fixture component.
Frequently asked questions about Fixture Bundle
- Is funddy/fixture-bundle compatible with Laravel?
- No. funddy/fixture-bundle is a Symfony2 bundle that relies on AppKernel registration, the Symfony DI container, and BundleInterface, none of which exist in Laravel. Laravel has no supported path to load a Symfony bundle, so it cannot be installed as a Laravel dependency. Treat it as a concept reference only, not a package you can require into a Laravel application.
- Can I install funddy/fixture-bundle with Composer in a Laravel project?
- Composer may technically resolve it, but that does not make it usable. The bundle expects Symfony kernel mechanics at runtime, so even a successful install leaves you with dead code. Symfony2-era version constraints are also likely to conflict with modern PHP and Symfony or Doctrine releases. If it does install, that is the dangerous half-working case rather than a green light.
- What does funddy/fixture-bundle actually do?
- The repository metadata only describes it as a fixtures bundle for the Funddy fixture component. It likely wraps fixture loading and management for Symfony, possibly around Doctrine data fixtures, with file-based definitions and console command execution. The exact feature set, ordering semantics, and persistence support are not documented in the available metadata. Confirm those details from the source before drawing any conclusion.
- What is the Laravel equivalent of funddy/fixture-bundle?
- Laravel's native equivalent is database seeders plus model factories backed by Faker. Seeders give you deterministic reference data and demo datasets, while factories generate realistic test rows. You can also read committed fixture files from disk inside a seeder if you need a curated dataset. This is the correct target architecture for a Laravel application.
- How do I migrate fixtures from a Symfony2 app to Laravel?
- Do not port the bundle, port the data. Extract your fixture content into a framework-neutral format such as YAML, JSON, or CSV, commit it to the repository, and write Laravel seeders that consume those files. This preserves the valuable artifact, which is the curated dataset, while discarding the delivery mechanism. The Symfony2 bundle has no future on the Laravel stack.
- Is funddy/fixture-bundle maintained?
- There are strong abandonment signals: roughly 3 stars, 0 dependents, and a Symfony 2.x target that reached end of life in 2018. Zero dependents means no downstream bug reports and no community scrutiny. There is no proxy for quality here, so assume it is unmaintained unless you verify recent commits yourself. Check the last commit date and composer.json constraints before relying on it.
- What are the alternatives to funddy/fixture-bundle?
- On Symfony, DoctrineFixturesBundle is maintained, widely adopted, and battle-tested, so prefer it unless you have a concrete capability gap. On Laravel, use database seeders, model factories, and Faker. Both alternatives have active maintenance and real production usage. If you cannot articulate what funddy/fixture-bundle provides that these do not, the evaluation ends there.
- Should I use funddy/fixture-bundle in production?
- No. Fixtures are development and test-time tooling, and this bundle should never become a runtime dependency of a deployed environment. With zero dependents there is no CVE history and no community security review surface to rely on. Keep the blast radius small: if you experiment at all, contain it to local tooling in a legacy Symfony2 context.
- Does funddy/fixture-bundle support PHP 8 and modern Symfony?
- Almost certainly not without a fork. Symfony2-era code implies PHP 5.x or 7.0-era constraints, and the bundle class, service configuration, and command registration would all need updating for Symfony 5, 6, or 7. Composer conflicts are the likely outcome on a modern codebase. The repository metadata does not state exact constraints, so read composer.json to confirm.
- Can I use funddy/fixture-bundle with Doctrine in Laravel?
- Laravel can use Doctrine through packages like Laravel Doctrine, but that does not make a Symfony2 bundle loadable. The blocker is the Symfony kernel and DI container integration, not the ORM. For Doctrine-backed Laravel projects, write seeders and Artisan commands against the Doctrine entity manager directly. Do not route fixture loading through a Symfony bundle.
Weaver
How can I help you explore Laravel packages today?