Weave Code
Jsrouting Bundle Laravel Package
funddy/jsrouting-bundle
Funddy JSRoutingBundle exposes Symfony routes to JavaScript, letting front-end code generate URLs from route names and parameters without hardcoding paths. It integrates with Symfony routing and provides a lightweight JS helper for client-side links, AJAX calls, and navigation.
Enables you to use your Symfony routes from JavaScript, allowing the generate routes in a very similar way. It supports static and dynamic routes generation.
Frequently asked questions about Jsrouting Bundle
- Can I use funddy/jsrouting-bundle in a Laravel application?
- No. funddy/jsrouting-bundle is a Symfony2 bundle, not a Laravel package. It has no service provider, facade, publishable config, or Composer extra.laravel block, so adding it to Laravel would require a rewrite rather than a configuration change. For Laravel route generation in JavaScript, use Ziggy.
- Does funddy/jsrouting-bundle support Laravel 10 or Laravel 11?
- No supported Laravel version exists for this package. It targets Symfony 2.x, and Symfony 2-era bundles routinely pin symfony/framework-bundle ~2.x with PHP 5.5–7.0 constraints. Those constraints conflict with modern Laravel requirements and can block PHP 8 upgrades in a Composer lock file.
- How do I install funddy/jsrouting-bundle?
- In a legacy Symfony2 application, install it with Composer and register the bundle through Symfony's AppKernel. It integrates through Symfony's Bundle class, dependency injection container compiler passes, and the kernel.request and route-dump lifecycle. There is no php artisan vendor:publish step because it is not a Laravel package.
- What is the Laravel equivalent of funddy/jsrouting-bundle?
- Ziggy is the Laravel-native equivalent. It exposes Laravel named routes to JavaScript, includes a Blade @routes directive, supports per-route filtering, and provides TypeScript types. Ziggy is actively maintained and purpose-built for Laravel, unlike this Symfony2 bundle.
- How does funddy/jsrouting-bundle expose routes to JavaScript?
- It dumps Symfony's route table to the client and provides a lightweight JavaScript helper to generate URLs from route names and parameters. It supports both static and dynamic route generation so front-end code can build links, AJAX calls, and navigation targets. This mechanism is Symfony-specific and has no Laravel integration in the package.
- Is funddy/jsrouting-bundle safe for production?
- Technical risk is high. The bundle works by dumping the route table to the client, and Symfony's default route table can include admin, internal API, and debug routes, making misconfiguration an information-disclosure finding. It also only fits Symfony 2.x, which reached end of life in November 2018 and has received no security fixes since.
- Does funddy/jsrouting-bundle work with dynamic route parameters?
- Yes, within Symfony2. The bundle supports static and dynamic route generation, so front-end code can pass parameters by route name. However, client-side route names are strings with no compile-time linkage to server-side definitions, so route renames fail at runtime in the browser rather than at build time. None of this applies to Laravel.
- What are the alternatives to funddy/jsrouting-bundle for Laravel?
- Ziggy is the recommended Laravel-native alternative. For legacy Symfony projects, FOSJsRoutingBundle is the more established option with a similar API shape. funddy/jsrouting-bundle has only 5 stars and 0 Packagist dependents, so production evidence for it is essentially absent.
- Is funddy/jsrouting-bundle maintained?
- There is no meaningful maintenance signal. It has 5 stars, 0 dependents, no release cadence, no maintainer signal, and no CVE intake process. If you vendor or fork it, remediation ownership falls on your team. Laravel teams should use Ziggy instead.
- Can I test funddy/jsrouting-bundle in a Laravel test suite?
- No. There are no Laravel test helpers, service provider bootstrapping, or facade fakes because it is a Symfony2 bundle. Testing it inside Laravel would mean porting its route-dump logic into Laravel idioms first. Any such port carries all the maintenance burden and the package itself contributes little beyond inspiration.
Weaver
How can I help you explore Laravel packages today?