Weave Code
Routing Bundle Laravel Package
modera/routing-bundle
Modera Routing Bundle adds flexible route management to PHP applications, with support for localized and dynamic routes, route caching, and easy integration into existing frameworks. It simplifies defining, matching, and generating URLs while keeping configuration clean and maintainable.
[READ-ONLY] Makes it possible for bundles to dynamically register routing resources with the need to have root app/config/routing.yml updated.
Frequently asked questions about Routing Bundle
- Is modera/routing-bundle a Laravel package?
- No. modera/routing-bundle is a Symfony bundle that hooks into Symfony's bundle and dependency-injection lifecycle through a Bundle subclass, a container compiler pass, and routing resource loaders. Laravel has no bundle abstraction and no central routing manifest, so there is no counterpart for it to plug into. If your application is Laravel, treat this package as not applicable.
- Can I install modera/routing-bundle in a Laravel application?
- You can try, but Composer will almost certainly block it: the last release dates from June 2016 and pins Symfony 2.x/3.x and PHP 5.x constraints that conflict with PHP 8 and Laravel 9, 10, or 11. Installing with --ignore-platform-reqs only pushes the failure into runtime. Even if it installed, it would register nothing in Laravel's router.
- What does Modera Routing Bundle actually do?
- It lets bundles in a Symfony application self-register their routing resources so the host app doesn't have to hand-edit app/config/routing.yml. It provides controller-based route definitions with grouping, per-bundle middleware and prefix configuration, and named route resolution helpers. In practice the whole capability is roughly 20 to 40 lines of resource-prepending logic.
- Is modera/routing-bundle still maintained?
- No. The repository is read-only and archived, the last release was 2016-06-10, and it has zero stars and zero dependents to validate against. There is no advisory feed, no maintainer on call, and no CVE response path. Adopting it is a fork-and-maintain commitment, not a dependency decision.
- How do I register package routes in Laravel without editing the host app's route files?
- In your package service provider, call $this->loadRoutesFrom(__DIR__.'/routes/web.php') and make a separate call for API or console route files. Laravel loads them during boot, keyed by the provider, so no host configuration is required. Add a route-name prefix to avoid collisions with application routes.
- How do I apply a prefix and middleware to package routes in Laravel?
- Wrap the route file call in Route::middleware([...])->prefix('vendor/package')->group(...) inside the service provider, or define the group inside routes/web.php itself. Prefixes, middleware, and name prefixes can all be driven from a publishable config file. This covers the per-bundle grouping the Modera bundle advertises, using only core Laravel.
- How do I handle localized and dynamic routes in Laravel?
- Laravel has no built-in localized route registration, so the usual pattern is a {locale} route parameter constrained by a regex and resolved in middleware, optionally with a package such as mcamara/laravel-localization. Dynamic segments are handled with route parameters and route-model binding. Modera Routing Bundle's localization support is Symfony-specific and does not carry over.
- How does route caching work and what invalidates it on deploy?
- Run php artisan route:cache during deployment to compile all routes into a single file, and php artisan route:clear to remove it. The cache reflects the compiled definitions, so any change to route code requires a fresh route:cache, and routes using closures cannot be cached at all. A package that registers routes at runtime from dynamic data will not survive caching.
- How do I test package routes in Laravel?
- Write feature tests that hit the registered routes with $this->get() or $this->post() and assert on status codes, JSON structure, and redirects. Use $this->assertRouteIs() or php artisan route:list to confirm each named route resolves as expected. Run the suite both with and without a cached route file so deployment caching does not mask failures.
- What are the alternatives to Modera Routing Bundle?
- On Laravel, service providers using loadRoutesFrom(), Route::group(), and a publishable config deliver the same outcome with zero third-party surface. On Symfony 5.3 or later, AbstractBundle::configureRoutes(RoutingConfigurator $routes) is imported automatically by the framework, and PrependExtensionInterface covers older 2.x/3.x applications. For a legacy Symfony app already depending on the bundle, vendor a pinned commit behind a thin adapter you control.
Weaver
How can I help you explore Laravel packages today?