- Is javihgil/nexmo-bundle a Laravel package?
- No. It is a Symfony2 bundle (Jgm\NexmoBundle) registered through AppKernel, with an Extension/Configuration pair and XML service definitions. There is no service provider, facade, or publishable config, so none of the idioms a Laravel integration needs are present.
- Can I install javihgil/nexmo-bundle in Laravel 10 or 11?
- No. Composer resolution is expected to fail because the constraints target Symfony 2.x and PHP 5.x and pull the nexmo/client v1 line, which pins Guzzle 5/6 and conflicts with Laravel 8+ (Guzzle 7, Symfony 5/6 components). Forcing install with --ignore-platform-reqs produces runtime class mismatches rather than a working integration.
- What Laravel and PHP versions does this package support?
- None that are current. It sits in the PHP 5.x and Symfony 2.x era and predates modern Laravel package conventions. Even inside a Symfony application it would only be viable on an end-of-life branch.
- Is javihgil/nexmo-bundle abandoned or still maintained?
- It is abandoned and archived, with its last release on 2016-03-01. There is no security disclosure path, no CVE patching, and no issue triage. It has roughly 7 stars and 0 dependents, so there is essentially no production signal.
- What should I use instead of javihgil/nexmo-bundle in a Laravel app?
- Use the current vonage/client major directly, or skip the SDK for simple SMS and call the REST API through Illuminate\Support\Facades\Http. Bind either behind a first-party SmsSender contract in a VonageServiceProvider. Configuration belongs in config/services.php reading from .env, which is the Laravel-native equivalent of what this bundle did for Symfony.
- How do I migrate the nexmo-bundle config and service wiring to Laravel?
- Treat the bundle as a reference implementation, not a dependency. Lift the config schema (api_key, api_secret, and any sender/from default) into a documented config block, and reimplement the client wrapper as a single injected service with an explicit interface. The reusable shape is roughly 100 to 200 lines.
- How do I test SMS sending in Laravel without hitting the network?
- If you call the Vonage REST API through the Http facade, use Http::fake() in your tests to assert the outgoing request. If you use the SDK, define an SmsSender interface and provide a FakeSmsSender implementation. Either way, no CI job should touch the network or need real credentials.
- Does this bundle support Vonage application ID and JWT auth or inbound webhooks?
- No. It wires the legacy nexmo/client v1 SDK and an API key/secret model. Vonage auth models have moved on, particularly application ID plus JWT for Messages, Voice, and Verify. Inbound webhooks such as delivery receipts and inbound SMS imply signature verification that you would have to own.
- Can I still use javihgil/nexmo-bundle in a Symfony application?
- Only on an end-of-life Symfony branch, and even then you inherit an EOL nexmo/client v1 dependency. For a maintained Symfony app, the equivalent move is plain service wiring in services.yaml against vonage/client or a currently maintained bundle. The bundle itself is best treated as reference material.
- What about 10DLC registration, Sender ID, and SMS compliance for Laravel projects?
- Those are procurement and compliance items that dwarf the library choice. US 10DLC and EU Sender ID registration depend on your geographies and sender obligations, and you should confirm who owns credential issuance and rotation and whether an existing Vonage contract exists. Decide whether you need a provider abstraction such as Twilio as a fallback before committing to a single vendor.