Weave Code
Routes Explorer Laravel Package
infyomlabs/routes-explorer
Laravel Routes Explorer adds a clean web UI for browsing every registered route in your app. Search, filter, and inspect URIs, names, middleware, and controller actions without artisan commands—handy for debugging and documenting large route tables.
Laravel Routes Explorer
Frequently asked questions about Routes Explorer
- What does infyomlabs/routes-explorer do and how is it different from php artisan route:list?
- It adds a web UI to your Laravel app that lists every registered route so you can browse, search, and filter them in the browser instead of scrolling terminal output. You can inspect URIs, route names, middleware, and controller actions at a glance. It complements artisan route:list rather than replacing it, and is most useful on large route tables where terminal output becomes unwieldy.
- How do I install infyomlabs/routes-explorer in a Laravel application?
- Install it as a development dependency with composer require --dev infyomlabs/routes-explorer, then rely on Laravel package discovery to register the service provider. If you need to change filtering, middleware, or the route prefix, publish the package config and assets with artisan vendor:publish. After that, hit the explorer endpoint in your browser and confirm the route resolves and lists your routes on the Laravel version you are targeting.
- Is infyomlabs/routes-explorer compatible with Laravel 10 and Laravel 11?
- The last release was February 2022, which places the package in the Laravel 8/9 era, so compatibility with Laravel 10 and 11 is not guaranteed. It may install cleanly under a permissive Composer constraint and still fail at runtime because Laravel's route registration and route-collection internals have changed since. Budget a short spike to install it against your actual target version and confirm the explorer view renders and lists routes correctly before committing.
- Which Laravel and PHP versions does routes-explorer actually support?
- Based on the February 2022 release date, expect the package to target Laravel 8 and 9 with the PHP versions those frameworks supported. There has been no release since, so no compatibility guarantee exists for newer Laravel or PHP releases. Check the composer.json constraints in the tagged release for the authoritative answer rather than assuming a permissive constraint means tested support.
- How do I secure or disable the routes explorer in production?
- Treat this as local and staging tooling only: it exposes a full inventory of route names, URIs, controller actions, and middleware, which is useful reconnaissance for an attacker. Gate the explorer route behind an environment check such as APP_ENV plus an auth middleware or explicit ability check. Also verify what the package's default authorization posture is when the config is unpublished, because an open-by-default route on an internet-facing box is a real exposure.
- How do I publish the routes-explorer config file and assets?
- Run php artisan vendor:publish and select the InfyOm routes explorer provider or tag from the prompt; publishing is optional and only needed if the defaults are insufficient. The config typically lets you control the explorer's route prefix, middleware, and which routes are hidden or filtered from the listing. Confirm the exact tag and available keys by inspecting the package's service provider after installation, since the published config is the source of truth.
- Can I search and filter routes by name, URI, middleware, or controller in the routes explorer?
- Yes. The web UI is built around search and filtering across the route table, so you can quickly narrow down routes by URI, route name, middleware, or controller action instead of scanning the full list. That is the main advantage over artisan route:list on applications with hundreds of routes, and it makes onboarding and debugging noticeably faster.
- Does routes-explorer work when routes are cached with php artisan route:cache?
- The package reads Laravel's registered route collection, which is still populated when routes are served from the compiled cache, so cached applications generally still show their routes. The caveat is how the package reads route properties: if it reaches into protected internals rather than public APIs, cached route objects can behave differently. Test the explorer once with route caching enabled in the environment where you plan to use it.
- What are the alternatives to infyomlabs/routes-explorer for viewing routes in Laravel?
- The built-in php artisan route:list command, including its JSON output, covers most needs and is guaranteed to stay compatible with your framework version. Laravel Telescope and IDE tooling such as the PhpStorm Laravel plugin provide route visibility without adding a UI package, and community options like pretty-routes offer a similar browser view. Choose the explorer only if a visual, searchable route table adds value your existing tooling does not cover.
- Is infyomlabs/routes-explorer actively maintained and safe to ship to production?
- The signals point to an unmaintained utility: roughly thirty-nine stars, zero dependents, and no release since February 2022, with no reliable security patch path. That profile fits an internal or demo tool that was open-sourced and left alone rather than a maintained package. Use it as a require-dev convenience behind an environment and auth gate, and keep it out of production request paths; removal is as simple as deleting the Composer line.
Weaver
How can I help you explore Laravel packages today?