The `nexmo-client` package provides a JavaScript SDK for integrating programmable conversation features, including in-app messaging and voice, into web and Node.js applications. While the package name is `nexmo-client`, it is functionally the predecessor to the Vonage Client SDK. The current stable version, 9.6.1, was last published over a year ago (as of 2026), indicating it is in a deprecated or maintenance state, with active development having shifted to the official `@vonage/client-sdk` package. It offers capabilities like offline message synchronization, push notifications, rich text and image support for messaging, and advanced in-app voice features such as group calling and user controls. Its primary differentiators lie in enabling robust real-time communication within applications through the Vonage API platform.
npm install nexmo-clientVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to install the `nexmo-client` package, import the `NexmoClient` class, and perform a basic login using a JWT. It includes error handling and logs connection status, fetching existing conversations as an example of post-login interaction.
Migrate your application to use the `@vonage/client-sdk` package. The API might have subtle differences, so review the `@vonage/client-sdk` documentation for migration guidance.
When seeking support or documentation, search for 'Vonage Client SDK'. Be aware that examples for the newer `@vonage/client-sdk` might not be directly compatible without adjustments.
Read the `LICENSE` file within the package or on the GitHub repository carefully to understand the legal implications and obligations before using in commercial or proprietary projects.
Always generate JWTs securely on your server-side application using your Vonage API key and secret. Pass the generated JWT to your client-side application for use with `client.login(JWT)`.
For browser usage via script tag, ensure `nexmoClient.min.js` is loaded before your script. For module environments (Node.js, bundlers), use `import NexmoClient from 'nexmo-client';` or `const NexmoClient = require('nexmo-client');`.Verify that your backend service is generating a valid, unexpired JWT with the correct Vonage application ID, private key, and standard claims (e.g., `exp`, `jti`, `iat`, `application_id`, `sub`, `acl`). Use JWT debuggers to inspect the token payload.
Ensure you are using the correct import syntax for your environment: `import NexmoClient from 'nexmo-client';` for ESM, or `const NexmoClient = require('nexmo-client');` for CommonJS. Avoid using named imports like `import { NexmoClient }` as the class is likely a default export.No dependency data recorded yet.