Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Typescript: message proprety does not exist on type 'Nexmo'

See original GitHub issue

With the following code:

import Nexmo from 'nexmo';
const nexmo = new Nexmo({
  // @see https://github.com/Nexmo/nexmo-node/issues/277
  applicationId: '',
  apiKey: 'xxx',
  apiSecret: 'xxx',
});
nexmo.message.sendSms('test', '620919191', 'this is a test');

I have:

TS2339: Property 'message' does not exist on type 'Nexmo'

Because of that, the library is unusable at all.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

ecwynecommented, Mar 5, 2020

@AlexLakatos is there any interest in converting the entire project to Typescript? The current structure would be map fairly easily, and it’s much easier to keep ts docs up to date and correct that way.

I would be happy to take a look at setting it up if you let me know which branch I should use as a base

1reaction

soullivaneuhcommented, Nov 29, 2019

I’m on a really no time moment sorry. If the issue is still not resolved when I’ll have more time, I’ll notify you about starting a work on it. 👍

Top Results From Across the Web

Property 'code' does not exist on type 'Error' - Stack Overflow

I get a Typescript error because the property 'code' does not exist on type 'Error'. this.authCtrl.login(user, { provider: AuthProviders.

How to fix 'Property does not exist on type Window in ...

Fixing the 'Property does not exist on type Window in TypeScript' error ... Fortunately for us, the fix is quite simple and involves...

[@types/express] Latest types throw Property 'headers', 'body ...

My builds are throwing the following errors after upgrades to latest version of the @types/express package: Property 'headers' does not exist on type...

Property 'status' does not exist on type 'Error' in TS | bobbyhadz

The error "Property 'status' does not exist on type 'Error'" occurs because the status property is not available on the Error interface.

API Errors - Vonage API Developer

When a Nexmo API returns an error, for instance, if your account has no ... The API key provided does not exist in...