- Is makasim/yadm-bundle a Laravel package?
- No. makasim/yadm-bundle is a Symfony bundle that provides a DI extension, configuration tree, compiler passes, and console commands for the framework-agnostic yadm MongoDB document mapper. It ships no Laravel service provider, facade, or config file, so installing it in a Laravel app adds no usable integration. For Laravel, treat only the core yadm library as a candidate and write your own binding.
- Can I install makasim/yadm-bundle in a Laravel application?
- Composer resolution will usually fail. The bundle's constraints were last updated in May 2019 and pin symfony/framework-bundle, symfony/dependency-injection, and symfony/config to the 3.4/4.x line with PHP 7.x, while a modern Laravel app pulls Symfony 6.x/7.x components transitively. Forcing it with --with-all-dependencies leaves two incompatible Symfony majors in the tree, and the bundle's Symfony kernel hooks remain inert in Laravel anyway.
- What Laravel versions does yadm-bundle support?
- None officially. The last release was May 2019, which predates Laravel 6, and there is no Laravel support matrix, service provider, or documentation for Laravel versions. The package targets Symfony 3.4/4.x applications, so any Laravel version claim would be unsupported.
- How do I install and configure yadm-bundle?
- In a Symfony app you install it with Composer, register the bundle in the kernel, and configure mapping and service registration under the bundle's config key. That registration path depends on Symfony's DI container and compiler passes. Laravel has no equivalent bundle registration mechanism, so the same steps cannot be reproduced there without writing the integration yourself.
- Does yadm-bundle work with PHP 8.1 or PHP 8.2?
- Unvalidated and risky. yadm's hydration relies on reflection and generated object construction, which is exactly the surface affected by PHP 8.x changes such as the ReflectionParameter::getClass() deprecation, typed property semantics, and dynamic property deprecation. Expect fatal errors or silent mis-hydration on PHP 8.1+ until patched, so run a spike on your real document shapes before trusting it.
- Is makasim/yadm-bundle still maintained?
- Effectively no. The last release was May 2019, the repository has roughly seven stars and zero dependents, and it is a single-maintainer project with no evident roadmap or upstream security response path. Treat it as abandoned and do not put it into production without forking and hardening it under the MIT licence.
- What is a maintained alternative to yadm-bundle for Laravel and MongoDB?
- Use mongodb/laravel-mongodb, the official and actively maintained Laravel MongoDB package, or go with raw mongodb/mongodb plus a thin repository layer of your own. Both avoid the Symfony bundle glue and the PHP 8 reflection problems entirely. Benchmark them on your real document shapes before accepting any 'extremely fast' claim from yadm.
- Do I need ODM features like identity map and unit of work in Laravel?
- Only if you actually need them. If your workload is ordinary CRUD, a thin repository over mongodb/mongodb is simpler and avoids ODM overhead. If you need identity map, unit of work, references, and lifecycle events, the official Laravel MongoDB package covers those semantics on a maintained driver. yadm's speed advantage is unbenchmarked in most contexts and may be reproducible with lean projections.
- How should I test or spike the yadm core library in a Laravel app?
- Decouple the decision first. Bind the core yadm DocumentManager behind your own interface in a Laravel service provider so the persistence engine is swappable, then write integration tests that hydrate and persist your real document shapes on the exact PHP and ext-mongodb versions you deploy. Add benchmarks against mongodb/laravel-mongodb and raw driver projections, and keep the adapter boundary so you can swap it out without touching domain code.
- What are the production risks of using yadm-bundle?
- Several. The bundle is abandoned, has no security patch path, pins a pre-driver-major mongodb/mongodb and old ext-mongodb assumptions, and depends on reflection-based hydration that breaks on PHP 8.x. It is also a single-maintainer project, so bus factor and dependency-policy sign-off are real blockers. If you must proceed, fork it, patch PHP 8 and driver compatibility, and isolate it behind an internal repository interface.