Weave Code
Pinkfire Bundle Laravel Package
pinkfire/pinkfire-bundle
Symfony bundle that integrates Pinkfire with your application, providing configuration, service wiring, and convenience tooling so you can add Pinkfire capabilities with minimal setup. Install via Composer, enable the bundle, and adjust the provided options to fit your project.
Symfony bundle to integrate support of Pinkfire
Frequently asked questions about Pinkfire Bundle
- Can I use pinkfire/pinkfire-bundle in a Laravel application?
- No. pinkfire/pinkfire-bundle is a Symfony bundle that hooks into Symfony's kernel and event system, not Laravel's service container or middleware pipeline. There is no adapter or Laravel service provider, so it cannot be installed or bootstrapped as a Laravel package. For Laravel, use Laravel Telescope, Sentry, or OpenTelemetry instead.
- Does pinkfire/pinkfire-bundle support Laravel 10 or Laravel 11?
- No. The package has no Laravel support at all and is not published as a Laravel package with a service provider or facade. Its Composer constraints target Symfony 2.x-era components and PHP 5.x, so installation will not resolve against a modern Laravel 10 or 11 lockfile. You should not attempt to add it to a Laravel project.
- Is the Pinkfire hosted service still online?
- The Pinkfire SaaS profiler appears to be defunct, and the bundle's core purpose is sending profiling data to that external backend. Without an operational endpoint, the bundle can compile but will fail silently or noisily at runtime. Verify service availability and ownership before considering any legacy use, and do not send request or SQL data to an unverified endpoint.
- How do I install pinkfire/pinkfire-bundle?
- The historical install path was Composer require pinkfire/pinkfire-bundle followed by enabling the bundle in the Symfony kernel. On modern PHP and Symfony versions the dependency resolution will likely fail because the package targets PHP 5.3 to 5.6 and Symfony 2.1 to 2.8. There is no maintained installation path for Laravel or current Symfony.
- Which PHP and Symfony versions does pinkfire/pinkfire-bundle support?
- It is a Symfony 2.x-era bundle, so expect PHP 5.3 to 5.6 and Symfony roughly 2.1 to 2.8 constraints. It is not compatible with Symfony 5, 6, or 7 without a rewrite, and it will not resolve on PHP 8+ projects. Check the original composer.json for exact constraints if you are auditing a legacy app.
- Is pinkfire/pinkfire-bundle abandoned?
- Yes, for practical purposes. It has very low adoption, no dependents, and no visible maintenance or security patch cadence. The upstream Pinkfire service is also defunct, which removes the bundle's reason to exist. Treat it as abandoned and plan removal from any legacy codebase.
- What should Laravel developers use instead of Pinkfire?
- Use Laravel Telescope for local development insight into requests, queries, jobs, and logs. For production error tracking and tracing, use Sentry or OpenTelemetry. For performance profiling, consider Blackfire or XHProf/Tideways depending on your environment. These tools are actively maintained and integrate cleanly with Laravel.
- Is it safe to install pinkfire/pinkfire-bundle in production?
- No. The bundle executes inside the application's request lifecycle and may transmit debug payloads such as request data, configuration, and SQL to a third-party endpoint whose ownership and status cannot be verified. With no maintenance or CVE response, it is a supply-chain and data-leakage risk. Do not add it to production or pre-production environments.
- Can pinkfire/pinkfire-bundle work with Symfony 6 or Symfony 7?
- No, not without a rewrite. The bundle uses Symfony 2.x service definitions and kernel.event_listener tags, and its Composer constraints conflict with modern Symfony components. A modern Symfony app should use the built-in Profiler and Web Profiler bundle instead.
- How do I remove pinkfire/pinkfire-bundle from a legacy Symfony 2 application?
- First inventory the app and confirm whether the bundle is wired in the kernel and service configuration. Remove the Composer dependency, the bundle registration, and any Pinkfire-specific configuration or event listeners, then rebuild the container cache. Replace the debugging capability with Symfony Profiler for local development and Sentry or OpenTelemetry for production telemetry.
Weaver
How can I help you explore Laravel packages today?