- Can I use kch/smsapi-bundle in a Laravel application?
- No. kch/smsapi-bundle is a Symfony 2 bundle, and its value is Symfony Dependency Injection wiring such as a Bundle class, services.xml, a Configuration tree, and a compiler pass. Laravel has no bundle or compiler-pass model, so none of the bundle code executes under Laravel. The only reusable part is the underlying SMSApi PHP client, which you can install directly.
- How do I install kch/smsapi-bundle with Composer?
- Running composer require kch/smsapi-bundle will install the bundle and its Symfony dependencies, but in Laravel it will be inert with no auto-discovery, registration, or config publishing. There is no supported Laravel integration path. For Laravel you should install smsapi/php-client instead and wire it yourself.
- Does kch/smsapi-bundle support Laravel 10, 11, or 12?
- No. The last release was 2016-06-01, it targets Symfony 2 which reached end of life in November 2018, and it constrains PHP to 5.x-era versions with Guzzle 3 or 5. Modern Laravel requires PHP 8.1 or 8.2 and Guzzle 7, so Composer resolution will fail or force risky platform-req workarounds.
- What is the Laravel equivalent of a Symfony bundle like this?
- In Laravel the equivalent is a service provider that binds the SMSApi client as a singleton, a config/smsapi.php file for credentials, and optionally a facade for convenient access. You would also usually wrap the client behind your own SmsSender interface. That is roughly an afternoon of work, not an integration project.
- Is kch/smsapi-bundle still maintained?
- No. It has not had a release since 2016, has one star and zero dependents, and shows no test suite or CI. There is no maintainer actively triaging issues and no disclosure channel for vulnerability reports. Treat it as an abandoned private package that happened to be published.
- Should I use the bundle or the SMSApi PHP client directly in Laravel?
- Use the SMSApi PHP client directly, or call the SMSAPI REST API over HTTP if the SDK is not PHP 8 compatible. The bundle adds only container wiring you would rewrite anyway. Verify the client library is maintained and compatible with your PHP version before adopting it.
- Will installing kch/smsapi-bundle conflict with my Laravel dependencies?
- Very likely. Symfony 2-era packages pin old PHP constraints and Guzzle 3 or 5, while modern Laravel needs PHP 8.1+ and Guzzle 7. Composer will either fail to resolve or you will be tempted to use --ignore-platform-reqs, which introduces runtime risk. Avoid that workaround in production.
- How do I configure SMSAPI credentials in Laravel?
- Do not rely on the bundle's Symfony Configuration tree or services.xml. Instead create a config file, read values from environment variables, and bind a configured SMSApi client as a singleton in a service provider. This keeps credentials out of code and makes the client easy to fake in tests.
- How do I test SMS sending in Laravel if I use this bundle?
- You cannot meaningfully test the bundle in Laravel because it ships no Laravel integration or test suite. The practical approach is to define your own SmsSender interface, implement it with the SMSApi client, and swap in a fake or use Laravel's HTTP fake in tests. That keeps your test suite fast and provider-independent.
- What are the alternatives to kch/smsapi-bundle for sending SMS in Laravel?
- The realistic options are the smsapi/php-client library wrapped in your own service provider, direct HTTP calls to the SMSAPI REST endpoints, or a maintained Laravel notification channel or SMS package. Whatever you choose, abstract it behind an interface so you can swap providers without touching call sites. Given SMSAPI is a Polish provider, also confirm sender-name rules and pricing for your market.