- Does pablodip/module-bundle work with Laravel?
- No. pablodip/module-bundle is a Symfony2-era bundle that depends on Symfony bundle registration in AppKernel, DI container extensions, Symfony config schemas, and Symfony route loaders. Laravel has no architectural seam for those APIs, so there is no supported integration path. Making it work would require a bespoke compatibility bridge that is worse than writing a native module convention.
- What Laravel versions does pablodip/module-bundle support?
- None. The package predates modern Laravel and targets Symfony 2.0/2.1-era APIs, with no Laravel service provider, package discovery, route integration, or container contract. The PHP package label is misleading because PHP does not imply framework portability. Do not treat it as a Laravel-compatible dependency.
- How do I install pablodip/module-bundle with Composer?
- You can run composer require pablodip/module-bundle only in a legacy Symfony2 application that satisfies the PHP and Composer constraints in the repository's composer.json. In a Laravel application there is no service provider or auto-discovery entry, so installation alone will not wire anything up. Verify the runtime constraints first because the targeted PHP version band predates modern runtimes.
- Can I use pablodip/module-bundle to organize Laravel modules?
- Not directly. Its module concept depends on Symfony bundle registration, per-module configuration, and Symfony route loading, none of which exist in Laravel. For Laravel, implement a native convention using service providers, namespaced directories, and route files, which typically takes about 50 to 100 lines. Treat the bundle as reference material rather than a dependency.
- Is pablodip/module-bundle actively maintained?
- There is no evidence of active maintenance, vendor backing, or a security response process. The repository has roughly 15 stars and 0 dependents, which means almost no downstream validation and no one else finding or fixing bugs. If you adopt it, you effectively become the de facto maintainer of an unpaid dependency.
- What are the alternatives to pablodip/module-bundle for Laravel?
- The most reliable alternative is Laravel's own service providers, package discovery, and route files, organized with a small in-house module convention. Community modular packages exist, but evaluate their maintenance and Laravel version support the same way you would any dependency. The underlying requirement is usually organize features into modules, and that does not require this bundle.
- How do I configure pablodip/module-bundle?
- In Symfony2 you configure it through bundle registration in AppKernel and the bundle's DependencyInjection extension and config schema. Laravel has no equivalent bundle registration or Symfony-style extension loading, so there is nothing to configure there. This is one of the main reasons the package cannot be dropped into a Laravel application.
- How do I test modules built with pablodip/module-bundle?
- Testing only makes sense inside a Symfony2 application using PHPUnit and Symfony's test client against the kernel. There is no Laravel testing integration, facade support, or HTTP test helper compatibility. For Laravel modules, test through Laravel's HTTP tests and container bindings instead.
- Is pablodip/module-bundle production ready?
- Only for a frozen Symfony2 legacy codebase where the cost of removal exceeds the cost of leaving it in place. Otherwise it carries high adoption, platform, and support risk because Symfony2 is end-of-life and the package has no active maintainer. It is not appropriate for a Laravel production application.
- What Symfony versions does pablodip/module-bundle support?
- It targets the Symfony2 era, circa Symfony 2.0 and 2.1, and relies on APIs that no longer exist in Symfony 3 and later. It is not compatible with Symfony 5, 6, or 7, and the PHP version band it expects predates modern runtimes. Check the repository's composer.json for the exact constraints before considering it for legacy work.