Weave Code
Cache Info Bundle Laravel Package
mapado/cache-info-bundle
A Symfony bundle that surfaces cache information in your app, adding a cache panel to the web debug toolbar and profiler so you can inspect cache pools, hits, misses, and stored items while debugging.
Http cache info on top on Symfony Framework Bundle
Frequently asked questions about Cache Info Bundle
- Is mapado/cache-info-bundle compatible with Laravel?
- No. It is a Symfony FrameworkBundle extension that registers through bundles.php, while Laravel uses service providers and Composer auto-discovery. The package has no ServiceProvider and no extra.laravel block, so a Laravel install would not wire up any cache inspection. Treat it as Symfony-only and not applicable to a Laravel product.
- How do I install mapado/cache-info-bundle in a Laravel app?
- Do not install it in a Laravel app as a functional dependency. Composer may resolve it, but there is no Laravel service provider or auto-discovery entry, so it would register nothing at runtime. It can also collide with the Symfony component versions Laravel 10 and 11 already pin. If you need a reference, inspect the source rather than adding the package.
- What does mapado/cache-info-bundle actually do?
- It is a Symfony bundle that surfaces cache information for your application, including a web debug toolbar and profiler panel for inspecting cache pools, hits, misses, and stored items. It hooks Symfony's HttpKernel, HttpCache, and Store to expose that data. In Laravel there is no equivalent bundle registry or default Symfony reverse proxy, so it has nothing to inspect.
- Does mapado/cache-info-bundle support Laravel auto-discovery?
- No. The composer.json has no extra.laravel block and the package ships no Laravel ServiceProvider, so auto-discovery registers nothing. Laravel's bootstrap/app.php and provider model do not map to Symfony's registerBundles() and DI extension flow. Any manual wiring attempt would be unsupported and unvalidated.
- Can it inspect Laravel cache pools like Redis, file, or database?
- No. The bundle introspects Symfony HttpCache Store instances, not Laravel's Redis, file, or database cache stores. Laravel does not run the Symfony reverse proxy by default, so the bundle would have no cache store to report on. Use Laravel Telescope, Debugbar, response-cache middleware, or a small custom middleware instead.
- What Laravel and PHP versions does mapado/cache-info-bundle support?
- There is no supported Laravel version. It is a Symfony 3/4-era FrameworkBundle extension with legacy Symfony component constraints. There is no confirmed PHP 8.2 or 8.3 coverage, no Laravel 10/11 testing, and no deprecation testing. The upstream repository is archived, so compatibility work is not happening.
- Is mapado/cache-info-bundle safe for production?
- No. The upstream project is archived with no maintainer, no security patching, and no incident escalation path. It has 1 star and 0 dependents, so its failure surface is essentially untested in the wild. It also surfaces cache keys and hit rates, which should be internal-only diagnostics rather than exposed in production.
- What are Laravel alternatives for debugging cache behavior?
- Use Laravel-native observability first: Telescope, Debugbar, log channels, APM, and CDN analytics. If you are debugging response caching, spatie/laravel-responsecache or your own terminable middleware can expose HIT/MISS, key, TTL, Age, and Cache-Control headers. For Symfony services that genuinely run HttpCache, evaluate FOSHttpCache and Symfony's HttpCache docs rather than this archived bundle.
- How would I build similar cache diagnostics in Laravel?
- Build a terminable middleware that reads the resolved response's cache headers and appends X-Cache-Status, X-Cache-Key, and X-Cache-TTL. Gate it behind a config flag and app()->isLocal(); in Laravel 11 use appendIf(...) in bootstrap/app.php, and in Laravel 10 gate it in Kernel::middleware. Keep the output internal-only and avoid leaking cache keys on public responses.
- Will installing mapado/cache-info-bundle conflict with Laravel's Symfony dependencies?
- Likely. Laravel 10 and 11 already pin specific Symfony component versions, and this bundle carries legacy Symfony 3/4-era constraints. Composer resolution may fail or force downgrades elsewhere in the application. Even a successful install should be treated as unvalidated, not as working cache diagnostics.
Weaver
How can I help you explore Laravel packages today?