@types/jsonwebtoken has broken backward compatibility

[eliprand]

• I tried using the @types/jsonwebtoken package and had problems.
• I tried using the latest stable version of tsc. https://www.npmjs.com/package/typescript
• I have a question that is inappropriate for StackOverflow. (Please ask any appropriate questions there).
• Mention the authors (see Definitions by: in index.d.ts) so they can respond.
  • Authors: @mdebruijne and @andy-ms

The change introduced 4 days ago with this commit has broken backwards compatibility. It is not accepting generic objects such as {id:1234}.

The following line of code:
const signed = jsonwebtoken.sign({id:1234}, 'secret');

gets the following error:
Object literal may only specify known properties, and 'id' does not exist in type 'string | object | Buffer'.

Using tsc 2.2.2 same results at tsc 2.3.4

I believe this was mentioned in #16989

[ghost]

Should be fixed by microsoft/TypeScript#16290. Please try it out with typescript@next once that's in.

[eliprand]

@andy-ms I will revert to 7.2.0 for now until the next release of TypeScript comes out. ETA?

[mdebruijne]

As @andy-ms mentioned, this is due to a bug in TypeScript (microsoft/TypeScript#16235)

The workaround is to use type inference (or casting), for example;

const payload = { "foo": "bar" }

jwt.sign(payload, secret)

[orta]

Hi thread, we're moving DefinitelyTyped to use GitHub Discussions for conversations the @types modules in DefinitelyTyped.

To help with the transition, we're closing all issues which haven't had activity in the last 6 months, which includes this issue. If you think closing this issue is a mistake, please pop into the TypeScript Community Discord and mention the issue in the definitely-typed channel.