- What is pbxg33k/flaresolverr-bundle and what does it do?
- It is a small Symfony bundle that integrates FlareSolverr, a proxy service that drives a headless browser to solve Cloudflare and similar anti-bot challenges. The bundle wires the solver into your application through service configuration and dependency injection, so you can fetch protected pages programmatically. It is not a Laravel package and ships no Laravel service provider or facade. The underlying capability is simply an HTTP call to a running FlareSolverr instance.
- Can I use flaresolverr-bundle in a Laravel application?
- Not directly as a native Laravel package, because it is built as a Symfony bundle and expects Symfony's bundle registration and container lifecycle. You can still consume FlareSolverr from Laravel by calling its HTTP API directly or by wrapping it in a small adapter class behind an existing interface. That approach avoids pulling Symfony bundle machinery into a Laravel app. Treat the bundle as reference documentation for how the FlareSolverr API is shaped rather than a drop-in Laravel dependency.
- How do I install flaresolverr-bundle with Composer?
- The usual command is composer require pbxg33k/flaresolverr-bundle, followed by registering the bundle in your Symfony kernel or bundles.php. Because the current release is 0.0.3, pin the exact version rather than relying on a caret range, since caret constraints on 0.0.x collapse to patch-only updates anyway. After install you still need to complete the package's documented manual configuration steps before it will work. Verify the PHP requirement declared in its composer.json against your runtime.
- Do I need a running FlareSolverr server to use this package?
- Yes. The bundle is only a client; the real work is done by a separate FlareSolverr service that runs headless Chromium. That service has meaningful memory and CPU cost, so plan for a dedicated container or host and a network path from your app to it. Without a reachable FlareSolverr instance the bundle has nothing to talk to, regardless of how it is configured.
- Which PHP and Laravel versions does flaresolverr-bundle support?
- There is no published, tested compatibility matrix, and the package is still at 0.0.x ahead of a 1.0.0 release. Check the composer.json constraints for the PHP and Symfony component versions it actually requires. The TPM assessment explicitly flags the tested version matrix as an open question. For a Laravel app, verify behaviour on your exact PHP version in a sandbox before relying on it anywhere else.
- Why does the configuration file require manual steps?
- The release notes for 0.0.3 state that the shipped config/package/flare_solverr.yaml is not yet proper and currently requires manual actions. In practice that means a fresh install is not fully reproducible without out-of-band edits, which is a real risk for automated deploy pipelines. Commit your own checked-in config and encode any manual step as an explicit deploy task. Revisit this once 1.0.0 ships with a generated or corrected config file.
- Is flaresolverr-bundle 0.0.3 stable enough for production?
- It is self-described as pre-1.0 and has not established a stability contract. The project has a single maintainer and a very small, two-commit release cadence, and 0.0.3 was labelled a final-touches release without enumerated breaking changes or new APIs. Treat it as a viability spike rather than a production dependency. If you adopt it, pin the exact version and plan a contingency for vendoring or forking.
- How are FlareSolverr failures and retries handled in this bundle?
- The available material does not confirm whether the bundle surfaces FlareSolverr errors as framework exceptions or integrates with an HTTP client's retry and logging stack. That is listed as an open question to resolve before adopting it. If you do use it, put the package behind a single wrapper service in your application so error handling, timeouts and logging are controlled in one place. Test failure modes such as an unreachable solver, a timeout and an unsolved challenge explicitly.
- How does this compare to calling the FlareSolverr HTTP API directly?
- Calling the API directly from a small adapter gives you full control over timeouts, retries, logging and error mapping, and removes a pre-1.0 dependency from your stack. The bundle's value is convenience: it wires the solver into a Symfony container with minimal setup. Because the actual FlareSolverr interaction is a simple HTTP request, many teams will find a thin hand-written client easier to maintain than a 0.0.x bundle. Either way, keep the integration behind a single seam in your code.
- What should I plan for when flaresolverr-bundle reaches 1.0.0?
- The 1.0.0 release is expected to fix the configuration-file gap and may carry signature changes, so pin the exact 0.0.x version until then. Adopt it only in a sandbox or non-production app and build one thin wrapper service so call sites do not depend on package internals. Once 1.0.0 ships with a proper generated config, review the changelog and expand usage incrementally. Do not sequence a broad rollout ahead of that release.