Weave Code
Module Bundle Laravel Package
modera/module-bundle
Modera Module Bundle provides a modular structure for PHP applications, letting you organize features into self-contained modules with configuration, dependency handling, and lifecycle hooks. It helps keep large codebases maintainable, reusable, and easier to extend.
Adds support for dynamical bundles installation.
Frequently asked questions about Module Bundle
- Is modera/module-bundle a Laravel package?
- No. It is a Symfony 2/3-era Composer bundle whose only real behavior is a script handler that rewrites AppKernel::registerBundles() after install or update. Laravel has no AppKernel and no equivalent hook, so there is no production code path where this package can run in a Laravel app. For Laravel, provider registration is handled natively by extra.laravel.providers, bootstrap/providers.php, and php artisan package:discover.
- Can I install modera/module-bundle in Laravel 10 or 11?
- You should not. The package has no branch targeting current Laravel versions, will not satisfy Composer platform constraints on PHP 8.x, and would be an unsupported-code audit finding. If you need modular package registration, use Laravel's built-in package discovery and a ModuleServiceProvider instead of adding this dependency.
- What does modera/module-bundle actually do?
- Its real function is a Composer script handler that mutates a Symfony AppKernel file to register bundles automatically after install or update. That capability mirrors what Laravel already does natively through package discovery. The package does not provide a Laravel module system, service provider registry, or configuration layer of its own.
- Does modera/module-bundle support PHP 8?
- No. The last release was 2016-06-13, it predates PHP 7 type declarations and modern PSR-4 conventions, and there is no branch for current PHP or framework versions. Expect Composer platform refusal on PHP 8.x and incompatibility with Symfony 4+ or Flex. There is no maintainer or patch channel to move it to a supported state.
- What is the Laravel equivalent of modera/module-bundle?
- Laravel's native package discovery, available since 5.5, is the direct equivalent for automatic provider registration via extra.laravel.providers and php artisan package:discover. For modular application structure, use nwidart/laravel-modules or an in-house ModuleServiceProvider that reads a config, database, or deploy-time manifest. None of these require source mutation or a Composer install hook.
- Is modera/module-bundle maintained?
- No. The repository is archived, the last release was 2016-06-13, and it has zero stars, zero dependents, and a score of 0.015. There is no active maintainer, no release path, and no community patch channel. Treat it as a historical reference rather than a dependency.
- Is modera/module-bundle safe for production?
- No. Its install-time source-code mutation conflicts with reproducible builds and immutable containers, and it creates boot-time failure modes where the whole application can fail rather than degrade. Zero downstream users means zero production validation. For a Laravel target, adding it would be a negative-value audit finding.
- How do I migrate from modera/module-bundle to Laravel package discovery?
- There is nothing to migrate in a Laravel app because the package does not run there. Implement registration through a ModuleServiceProvider that reads a registry such as config, a database table, or a deploy-time manifest and calls $this->app->register(). Then rely on bootstrap/providers.php and package:discover for package-level providers. For an inherited legacy Symfony app, inventory the dynamically injected bundles, codify them in config/bundles.php under Flex, remove the Composer hook, and verify with a cold-cache boot and cache:warmup.
- What alternatives should I use for modular Laravel backends?
- Start with Laravel's native package discovery and a ModuleServiceProvider backed by an explicit registry. If you want a larger module framework, evaluate nwidart/laravel-modules or build a manifest-driven registration layer in-house. These options preserve deterministic registration order, cache invalidation on install or remove, rollback on failed install, and no source mutation.
- Why is modera/module-bundle listed as a Laravel Composer package?
- That listing is a misclassification. The repository is a Symfony 2/3-era bundle, and its Composer hook targets AppKernel, which Laravel does not have. Before adopting it, confirm whether your target is Laravel or Symfony; if it is Laravel, re-scope the requirement to modular package registration and use native discovery.
Weaver
How can I help you explore Laravel packages today?