- Can I use jdecoster/router-extra-bundle in a Laravel application?
- No. This is a Symfony bundle built around the Symfony Router component, not a Laravel package, and Laravel has no extension point that consumes Symfony bundles. For Laravel, implement dynamic route registration natively through a RouteServiceProvider or routes loaded from persistence at boot.
- What does jdecoster/router-extra-bundle actually do?
- It extends Symfony's native routing with additional route loaders and convenience helpers for building route conditions. It integrates with the Router component so existing route configurations keep working while you gain extra utilities for more expressive route definitions. It is intended for Symfony applications, not Laravel.
- Does it support Laravel 10 or Laravel 11?
- No. The package is a Symfony bundle and does not provide Laravel service providers, facades, or any Laravel-specific integration. It cannot be installed as a normal Laravel Composer dependency and used through Laravel's router.
- Which Symfony and PHP versions does it support?
- The declared constraints are likely pinned to older Symfony 2.x or 3.x and may use PSR-0 autoloading, but you must verify composer.json before assuming compatibility. This is a vintage fork, so do not expect modern Symfony 6 or 7 support without upgrades. Check that its constraints resolve against your lockfile before any evaluation.
- Is jdecoster/router-extra-bundle actively maintained?
- Adoption signals are negative: one star, zero dependents, and no visible commit cadence, CI, or issue triage. It appears to be a single-maintainer fork with no evidence of production use. Treat it as unmaintained and unsuitable for new production dependencies.
- Does the package have a test suite?
- There is no meaningful test suite, so behavior must be established by reading the source. If you vendor any part of it, add characterization tests before relying on its routing behavior. Lack of tests is a major ownership cost for any team adopting it.
- What are the alternatives for dynamic routing in Symfony?
- Evaluate the maintained symfony-cmf/routing and symfony-cmf/routing-bundle packages first, since this fork appears descended from that lineage. Modern Symfony also provides native route loaders and route conditions that cover many advertised conveniences. Confirm whether your requirement is truly dynamic, data-driven routing before adding any package.
- How would I install and register it in a Symfony app?
- Installation would use Composer followed by bundle registration in registerBundles, plus service-definition reconciliation and version-constraint alignment. For forks of this vintage, expect to upgrade Symfony constraints and autoloading as part of integration. Because the fork is unmaintained, direct adoption is not recommended.
- Is it safe to use in production?
- Technical risk is high due to abandonment, unverified provenance, no test suite, and no security or CVE response capability. A low-visibility package in the request path creates supply-chain review liability that your team would absorb without any counterparty. Do not put it in production without vendoring and owning the code.
- How should I migrate off it or handle a specific patch I need?
- Do not adopt the fork directly. First confirm the product requirement, then evaluate the maintained CMF upstream; if the fork contains a specific patch you need, copy the relevant source into your own namespace, add characterization tests, and own it as first-party code with a known blast radius.