- Does madflow/alice-bundle work with Laravel?
- No. It is a Symfony bundle with a Bundle class, DI extension, and Symfony console commands, none of which Laravel recognizes. Its Alice integration is tied to the Symfony service container and Doctrine-style persistence. For Laravel, use Eloquent factories and fakerphp/faker, or wrap nelmio/alice standalone in an Artisan command with a custom persister.
- Can I use Nelmio Alice fixtures in Laravel without this bundle?
- Yes. nelmio/alice itself is framework-agnostic and can run behind an Artisan command. You will need to write an Eloquent persister because Alice's built-in persistence targets Doctrine. Treat that as an internal package or spike, not as a drop-in Composer dependency.
- How do I install madflow/alice-bundle?
- In Symfony, you would require the package with Composer, register the bundle, configure fixture paths and persistence, then run its console command. In Laravel there is no supported install path. Composer may resolve it, but the bundle will not register automatically and you would have to reimplement its Symfony wiring.
- What fixture formats does madflow/alice-bundle support?
- It supports YAML, JSON, and PHP fixture definitions through Nelmio Alice. Faker-powered generation produces realistic records. Configuration covers persistence and object-mapping options, but those options assume Symfony and Doctrine conventions.
- Is madflow/alice-bundle actively maintained?
- The available assessment shows 0 stars, 0 dependents, no visible maintainer, and no issue triage. It is a fork with high abandonment risk. Before approval, verify the upstream base commit, composer.json pins, and security response path. For production test suites, prefer maintained framework-native tooling.
- Which Laravel and PHP versions are supported by madflow/alice-bundle?
- The package is Symfony-oriented and the context lists no Laravel support, so assume none. It likely pins older PHP, Symfony, Alice, and Faker constraints, possibly fzaninotto/faker rather than fakerphp/faker. That can cause Composer conflicts on Laravel 9 or later. Check composer.json before trying it and do not assume PHP 8.x compatibility.
- Does madflow/alice-bundle require Doctrine, and can I use Eloquent instead?
- The bundle is built around Doctrine-style persistence and object mapping, and there is no documented Eloquent path. Using it in Laravel would mean either accepting Doctrine as a second ORM or writing a custom Eloquent persister. Both add architectural debt for a test-data concern.
- What are the best Laravel alternatives for fixture and test data generation?
- Laravel ships Eloquent model factories, fakerphp/faker, and seeders, which are idiomatic, maintained, and already known to the team. For complex relational graphs, multi-locale demo data, or shared fixture libraries, run nelmio/alice standalone behind an Artisan command. Avoid importing a Symfony bundle wrapper into an Eloquent codebase.
- Can I share Alice fixture files between Symfony and Laravel services?
- The YAML fixture DSL is portable, but the bundle wiring and Symfony-specific configuration are throwaway. You could keep Alice fixture files in a shared library and load them with a Laravel-specific Artisan command and Eloquent persister. That preserves the DSL without adopting the Symfony bundle.
- Is madflow/alice-bundle safe for production or CI use?
- It is MIT licensed, so licensing is compatible with commercial use, but supply-chain and maintenance risk are unquantified. An unmaintained dev or test dependency still needs security and licensing review. For CI, pin versions, audit Composer dependencies, and prefer maintained tooling. This bundle is not a low-risk drop-in for Laravel.