- Is hautelook/templated-uri-bundle a Laravel package?
- No. It is a Symfony Bundle that expects a Symfony Kernel, registration in config/bundles.php, and Symfony's RequestContext, none of which exist in Laravel. There is no service provider, facade, or framework-agnostic entry point, so installing it in a Laravel application gives you nothing the framework can bootstrap.
- Can I install hautelook/templated-uri-bundle in a Laravel application?
- You can attempt a Composer require, but resolution often fails because the bundle pins symfony/routing to older major versions while Laravel 11 and 12 require ^7. Even if it installs, Laravel has no bundle registration mechanism, so the router and generator are never wired up. The assessment lists Composer conflict risk as the top risk and the first thing to test.
- What is an RFC 6570 URI template and why would a Laravel API use one?
- RFC 6570 defines templates such as /users/{id}{?fields} that expand into concrete URIs from named parameters. They are useful for hypermedia APIs, HAL or JSON:API links, and consistent link generation where clients fill in variables. Laravel's route helper builds URLs from route definitions, not from arbitrary templates, so template expansion is a separate capability.
- Does this bundle match inbound URIs against URI templates or only generate them?
- The differentiator is matching: generation is commodity, matching is not. The README claims an RFC-6570 compatible router and URL generator, but the assessment notes that whether the underlying library actually matches inbound URIs against templates is unverified. Confirm that behavior before treating it as a routing layer.
- Which Laravel versions does this Symfony bundle support?
- None officially. It is a Symfony bundle with no Laravel support statement, and its composer.json constraints on PHP and symfony/routing were unverified at the 3.5.0 release. A 2023-era bundle commonly pins symfony/routing to ^4 or ^5, which conflicts with Laravel 11 and 12. Treat Laravel compatibility as unproven until you resolve it in a scratch project.
- What are the best alternatives to this bundle for Laravel?
- For expansion-only needs, rize/uri-template and league/uri are maintained, widely adopted, and easy to use inside Laravel without Symfony baggage. If you need the specific hautelook router behavior, extract hautelook/templated-uri-router v4 and wrap it in a small Laravel service provider. Vendor or fork the RFC 6570 code only if inbound template matching is a hard requirement.
- Can I use hautelook/templated-uri-router without the Symfony bundle?
- That is the preferred path if you want this codebase at all. The value lives in the underlying library, not the bundle wrapper, and the router is intended to be usable standalone. Read its composer.json first: version 4.0 may have modernized the PHP and symfony/routing constraints, which changes whether a Laravel 11 or 12 install can resolve.
- What changed in version 3.5.0 of templated-uri-bundle?
- The entire diff is a single dependency bump to hautelook/templated-uri-router 4.0, merged as PR #5. There are no new features, no Laravel affordances, and no framework-agnostic entry point. It is the only release activity since January 2023 and came from a first-time contributor, which is a weak but positive maintenance signal.
- How actively is hautelook/templated-uri-bundle maintained?
- Weakly. The bundle is effectively unused, 3.5.0 is the only activity since 2023-01-19, and one merged dependency bump is not a support program. The assessment also questions who the active maintainer is and whether a security disclosure channel exists. Assume you own every defect you encounter.
- Is the RFC 6570 support in this library actually complete?
- Unverified. A README-level claim of RFC-6570 compatibility says nothing about Level 3 or Level 4 operator support, reserved expansion semantics, or prefix modifiers. The router 4.0 major bump makes re-verification necessary rather than optional, because breaking semantic changes can reach you transitively through the bundle.