Weave Code
Frontend Url Bundle Laravel Package
genj/frontend-url-bundle
Symfony bundle for generating frontend URLs from your backend configuration. Define route mappings once and use its services and Twig helpers to build consistent, environment-aware links without hardcoding paths in templates.
Provides helpers to easily generate URLs for frontend routes from within an admin environment.
Frequently asked questions about Frontend Url Bundle
- Can I use genj/frontend-url-bundle in a Laravel application?
- No. Despite being catalogued as a Laravel/PHP package, this is a Symfony bundle: the repository name ends in Bundle, the package suffix is -bundle, and it follows Symfony bundle class conventions. There is no Laravel service provider, no publishable config, and no PSR-4 namespace intended for app/, so Laravel cannot boot it. Porting it would leave almost none of the original code intact, and Laravel already solves the same problem with native routing features.
- How do I install genj/frontend-url-bundle?
- You would install it with Composer using genj/frontend-url-bundle and then register the bundle in a Symfony AppKernel, which is the Symfony 2.x registration style it was built for. Expect composer require to fail on modern version constraints. A forced install would likely fail at container compilation or autoload, and none of this applies to a Laravel application.
- Which Symfony and PHP versions does this bundle support?
- It is pinned to Symfony 2.x bundle contracts and PHP 5.5/5.6-era code, with no return types or nullable types. The last release note reads "Last tag before upgrading to Symfony3," and that Symfony 3 migration was announced but never delivered, so the code never moved off Symfony 2.x. Symfony 5, 6, and 7 have removed or renamed the bundle APIs it depends on, and the code will not run cleanly on PHP 8.x without edits.
- Is genj/frontend-url-bundle still maintained?
- No. The repository is archived, with zero stars and zero dependents, and there is no successor release after the announced Symfony 3 upgrade was abandoned. That abandoned upgrade is the clearest signal of abandonment, since the maintainer's own stated next step never shipped. There is no upstream to file issues against and no maintenance path.
- What is the Laravel equivalent of generating frontend URLs from backend routes?
- Laravel handles this natively. You can define frontend routes with Route::domain(config('frontend.host'))->group(...) and then resolve them from an admin context using the route() helper, which works across domains without extra machinery. For non-route paths you can use URL::to() or a small FrontendUrl helper bound in the container, all driven by a single frontend.host or frontend.scheme config key. A package wrapper around the router abstraction adds no value here and would be net-negative complexity.
- Why is the 1.0.0 version tag of this bundle misleading?
- Semver convention reads 1.0.0 as a first stable release with an API commitment, but here it is functionally a tombstone. The release note says it is the last tag before an intended Symfony 3 upgrade that never happened, so it marks the final state of the Symfony 2.x line rather than maturity. Automated scoring that rewards a 1.x tag will overrate this package unless the tag semantics are recorded explicitly.
- Do the Twig helpers in this bundle work in Laravel Blade templates?
- No. The bundle ships Twig helpers tied to Symfony's templating layer and has no Blade directives or equivalents. In Laravel you would use the built-in route() and url() helpers instead. There is nothing in the package that integrates with Blade.
- Are there security risks to running this bundle in production?
- Yes, principally because it is archived and unmaintained with no CVE monitoring or security response path. URL generation helpers also touch redirect, scheme, and host handling, so unmaintained code in that seam carries open-redirect and host-header-poisoning exposure if it is ever wired to user input. Treating it as a dependency is not advisable; reading the source for ideas is the safer option.
- How would I test genj/frontend-url-bundle in a test suite?
- There is no documented test suite or CI for the package, and with the repository archived there is no upstream coverage to rely on. In Laravel you cannot test it at all, because the bundle cannot be booted by the framework. Any evaluation would require manually standing up a Symfony 2.x kernel just to exercise the mapping layer, which is not worth the effort given the native alternatives.
- What license is genj/frontend-url-bundle and can I reuse its code?
- It is MIT licensed, which is the one clean signal in the package and means legal reuse is permitted. Reading the source for ideas about route mapping is therefore safe. Taking it on as a Composer dependency is not recommended.
Weaver
How can I help you explore Laravel packages today?