- Can I use synaq/curl-bundle in a Laravel application?
- No, not as a package dependency. It is a Symfony2 bundle that registers itself in AppKernel and wires services through Symfony's DependencyInjection container, and Laravel has no equivalent bundle or kernel concept. Installing it would mean running two competing containers in one process or discarding everything that makes it a bundle. The only realistic reuse is copying the thin cURL client class into your own code.
- Is synaq/curl-bundle compatible with Laravel 10 or 11?
- Almost certainly not. The bundle targets Symfony2, which reached end of life in November 2018, and its composer.json very likely constrains symfony/framework-bundle to the 2.x line with PHP 5.x-era requirements. Those constraints will not resolve against a modern Laravel dependency graph, so Composer will refuse the install. Check the declared constraints on the repository before spending time on it.
- How do I install synaq/curl-bundle?
- The nominal command is composer require synaq/curl-bundle, followed by registering the bundle in AppKernel in a Symfony2 application. On a modern Laravel or Symfony runtime the dependency resolution will typically fail on PHP and framework version constraints. The recommended decision here is a no-install: do not add it to composer.json at all.
- Is synaq/curl-bundle still maintained?
- Effectively no. It has zero stars and zero dependents, a single maintainer, and a Symfony2 target that has been unsupported since 2018. No public issues or security review have exercised it against current PHP versions, and there is no path to upstream fixes. Treat any code you take from it as a fork you own and maintain yourself.
- What should I use instead of synaq/curl-bundle in Laravel?
- Use Illuminate\Support\Facades\Http, which is Guzzle-backed and ships with Laravel, or Guzzle directly if you want lower-level control. Both are actively maintained, well documented, and already cover TLS verification, redirects, streaming, cookie jars, and concurrent requests. Reproduce each of your call patterns with Http:: first and only port code if you find a genuine gap.
- How do I migrate from synaq/curl-bundle to Laravel's HTTP client?
- Start by grepping your codebase for the bundle's client class and any direct curl_* calls, then rewrite each distinct call pattern using Http:: or Guzzle and compare the responses. Put the transport behind an interface such as HttpTransport and bind it in a service provider so a later swap is a one-line container change. Document any pattern you cannot reproduce, because only that gap justifies keeping a port.
- Does synaq/curl-bundle support parallel requests and custom cURL options?
- The source would need to be read to answer definitively, but the reusable core is likely a class or two wrapping ext-curl handles with convenience methods. Guzzle already gives you concurrency through promise pools, per-request option passthrough, custom cookie jars, and timing instrumentation. In practice the low-level features you might want are available from a maintained library rather than this bundle.
- Is synaq/curl-bundle safe to use in production?
- The risk is maintenance rather than correctness. The code targets an end-of-life framework, has no dependents validating it against current PHP releases, and has had no public security review, so you would be shipping an unpatched fork with no upstream fixes. For production Laravel applications, prefer Guzzle or the built-in HTTP client and record any extracted code as technical debt with an owner and review date.
- Can I copy the cURL client class from synaq/curl-bundle into my app?
- Yes, the MIT license permits it and the extraction effort is measured in hours rather than weeks. Strip the Symfony Bundle and DependencyInjection Extension classes, move the client into app/Support/Http/ or a small first-party package, and bind it through a Laravel service provider. Keep it behind an interface so replacing it with Guzzle later stays a one-line change.
- How do I test a cURL client extracted from synaq/curl-bundle?
- Assume the upstream project has no meaningful tests, so write your own covering error paths, timeouts, redirects, and non-2xx responses rather than just the happy path. In Laravel, Http::fake() lets you assert outgoing requests and return stub responses without touching the network. If you keep the extracted class, hide it behind an interface and bind a fake implementation in the container for tests.