- How do I install apih/laravel-route-list-web?
- Install it with Composer using composer require apih/laravel-route-list-web. Package auto-discovery registers the service provider, so no manual provider entry is normally needed. After installing, publish the config file and register an authorization gate or middleware before opening the route list page in a browser.
- Does apih/laravel-route-list-web support Laravel 11 and Laravel 12?
- Check the package's composer.json for its declared Laravel and PHP constraints before adopting it, especially for Laravel 11 or 12. The package is a thin, framework-native layer over Laravel's route collection, but its low adoption means compatibility should be verified in your app rather than assumed. Test installation in a branch or staging environment first.
- Is the Laravel route list web page safe to expose in production?
- The page can reveal route URIs, HTTP methods, names, controller actions, middleware stacks, and parameter names, which is useful internally but sensitive if exposed publicly. Treat it as a developer-observability tool and protect it with an authorization gate or middleware. Do not leave it internet-reachable without an access review.
- Can I disable the route list page in production?
- The package publishes a config file, and the intended posture is to gate it per environment rather than expose it everywhere. You should confirm whether route registration can be disabled entirely via config in your version, and if not, restrict access with middleware or a gate. Many teams will want it enabled only in local, development, or staging environments.
- Does it work when php artisan route:cache is active?
- The package renders Laravel's existing route collection, so it should reflect the routes Laravel has registered for that request. With route caching enabled, verify in staging that the cached route set appears as expected rather than assuming parity with an uncached app. This is one of the edge cases worth checking because the package has limited community validation.
- What route details does the Laravel route list web UI show?
- It provides a searchable, filterable browser view of registered routes, including method, URI, route name, action, and middleware. This maps the application's internal surface, so it complements artisan route:list for human inspection. The CLI remains the better source for scripting and CI output.
- Does laravel-route-list-web handle apps with thousands of routes?
- The package is a Blade view over Laravel's route collection, so large route counts are mostly a question of UI performance and whether search and filtering are sufficient. The assessment notes that large route counts are an edge case unlikely to have been broadly exercised at 17 stars. Pilot it against your largest app and check pagination, search, and filtering behavior.
- How is apih/laravel-route-list-web different from artisan route:list?
- artisan route:list is a CLI command that remains the source of truth for scripting and CI, while this package adds a browser-based, searchable, filterable view for developers. It is additive and reversible: one Composer entry and a config file. It complements the CLI rather than replacing it.
- Does it show middleware groups, route names, domains, and vendor routes?
- The package is described as surfacing method, URI, name, action, and middleware for registered routes, but the assessment specifically flags middleware groups, domains, and vendor-published routes as things to verify. Confirm these details in a staging app with vendor routes and domain routing if they matter to your team. Do not assume full parity with every artisan route:list column.
- Is laravel-route-list-web well maintained and tested?
- The package is small and MIT-licensed, but at roughly 17 stars it has limited community validation and a single-maintainer profile. The assessment recommends checking test coverage and whether CI runs against multiple Laravel majors before treating it as a platform dependency. A pilot in dev or staging is the sensible posture.