Weave Code
Profiler Storage Bundle Laravel Package
sitetheory/profiler-storage-bundle
Sitetheory's Profiler Storage Bundle provides configurable storage backends for persisting profiler data in PHP applications. It lets you capture and retrieve profiling traces outside of memory, making it easier to inspect request performance across environments and storage drivers.
Profiler Storage Bundle for Symfony 2.8+
Frequently asked questions about Profiler Storage Bundle
- Is sitetheory/profiler-storage-bundle compatible with Laravel?
- No. It is a Symfony bundle built around Symfony's bundle system, dependency injection extension, compiler passes, and HttpKernel profiler APIs, while Laravel has no bundle lifecycle and uses service providers. It is not a Laravel-native package, so installing it directly is not recommended. You would need a fork or an internal adapter to reuse its storage mechanics in Laravel.
- How do I install sitetheory/profiler-storage-bundle in a Laravel app?
- You should not install it directly in a Laravel application because it has no Laravel service provider, package discovery entry, or Laravel configuration surface. Composer will likely pull Symfony framework components and create dependency conflicts with modern Laravel versions. If you need the capability, extract or reimplement the storage logic in a Laravel service provider instead.
- What Laravel and PHP versions does sitetheory/profiler-storage-bundle support?
- The package targets Symfony 2.8 and 3.x-era APIs and was last released in 2019, with PHP constraints likely pre-8.x. That makes it a poor fit for modern Laravel applications that require PHP 8.1 or newer. Check its composer.json and run composer why-not against your target app before any spike.
- Can I use Symfony profiler storage with Laravel Telescope or Debugbar?
- No. Telescope, Debugbar, and Clockwork are Laravel-native debugging tools with their own storage and inspection workflows. This bundle integrates with Symfony's profiler APIs, not Laravel's debugging ecosystem. Adopting it would add maintenance burden without filling a gap that those tools already cover.
- What are the best alternatives to sitetheory/profiler-storage-bundle for Laravel?
- Laravel Telescope, Laravel Debugbar, and Clockwork are the practical alternatives for profiling and debugging Laravel applications. They provide request inspection, storage, and UI tooling designed for Laravel's container and lifecycle. Use those unless you have a legacy Symfony service that genuinely needs this bundle.
- Is sitetheory/profiler-storage-bundle maintained and safe for production?
- The upstream is effectively abandoned: last release in 2019, 4 stars, and 0 dependents, so there is no community validation or realistic upstream support. The MIT license helps if you fork, but you would own security patching and compatibility testing. That is high risk for production use.
- How do I configure persistent profiler storage in Laravel?
- Laravel-native tools already provide persistent storage for profiling data, such as Telescope's database or cache-backed entries and Debugbar's storage options. Configure those tools through their published config files rather than trying to wire a Symfony profiler storage backend. If you need a custom store, implement it as a small Laravel service or adapter behind a config file.
- Why does Composer conflict when installing sitetheory/profiler-storage-bundle with Laravel?
- The bundle carries Symfony 2.8 and 3.x-era constraints, and installing it alongside Laravel would pull Symfony framework components that conflict with Laravel's dependencies. Modern Laravel projects require newer PHP and Symfony components, so Composer will likely block the install. Run composer why-not sitetheory/profiler-storage-bundle against your app to confirm the exact conflict.
- Can I fork or extract the profiler storage code into a Laravel service provider?
- Yes, that is the only realistic path if you genuinely need the capability. Audit the repository, separate Symfony-specific classes from the storage read, write, purge, and find semantics, and extract a standalone PHP adapter. Then wrap it in a Laravel service provider, publish a config file, bind it to a manager or facade, and add Artisan commands and tests for supported Laravel and PHP versions.
- Does sitetheory/profiler-storage-bundle work with Symfony 4, 5, or 6?
- It targets Symfony 2.8 and 3.x-era profiler APIs, and Symfony profiler storage interfaces and internals changed materially in later releases. The core classes may depend on contracts that were removed or deprecated after Symfony 3.4. Treat it as a legacy reference rather than a current Symfony or Laravel dependency.
Weaver
How can I help you explore Laravel packages today?