Type definitions do not match in version 1.4.1

[PCASME]

Using jsPDF version 1.41 (I think the problem also applies to version 1.4.0.)
Using @types/jspdf version v1.1.31 (AFAIK, no other version available).

Problem:

The types in v1.4.1 do not match with type definitions in @types/jspdf@1.1.31.

Sample:

const doc = new jsPDF();
console.log(doc.internal.pageSize.width);

Previous 1.4.1/1.4.0 the above code works as expected.
Property doc.internal.pageSize.width match with type definitions and exists as a property.
All is OK.

In version 1.4.1/1.4.0 the property doc.internal.pageSize.width does not exists and I must use the doc.internal.pageSize.getWidth() method instead. Doing this works but I get an error in the editor (VSCode) due to mismatching type definitions.

How can I solve this?
There is an updated version of type definitions?

Thanks in advance.

[Uzlopak]

What are "type definitions in @types/jspdf@1.1.31"?

[PCASME]

I'm working in an Angular project with TypeScript not plain JavaScript so...

In order for TypeScript to perform the type checking, the types need to be defined somewhere. It's pretty straightforward how to add type definitions to the variables declared in your own code, but how does TypeScript know about the types of variables and functions of existing JavaScript libraries?

This is where type definition files come into play. They allow you to provide type information for JavaScript code that is by itself (by its very nature) not statically typed. The file extension for such a file is .d.ts, where d stands for definition. Type definition files make it possible to enjoy the benefits of type checking, autocompletion, and member documentation.

See this: Using TypeScript's Type Definition Files to Get Tooling Support for Plain JavaScript

For jsPDF the type definitions are in the NPM package @types/jspdf file and the latest version is the v1.1.31 (AFAIK) but this do not match with the definitions in the jsPDF JavaScript library v1.4.1. That's the problem.

[PCASME]

Mainly the problem is that @types/jspdf is a separately definition file created and "mantained" by third party people.
Would be nice if type definitions for jsPDF were bundled with the library.

[Uzlopak]

The problem is that the functions in internal are no API. So actually you should not use the methods anyway....

[PCASME]

Yes, I saw the code and what it says about the API, that is intended for plugins...
But then how can I get the document dimensions instead?

[Uzlopak]

What about this stuff?

https://dev.to/_gdelgado/comment/33dd

Using jsDoc instread typed?

I added a huge load of jsDoc to the project with #1944

Secondly, yeah i guess there is a need of a getPageSize-API and setPageSize-API like suggested in #825

[PCASME]

Thanks for the note on jsDoc.
I remain alert for a possible inclusion of pageSize in the API, meanwhile using internal.pageSize works for me.

[Uzlopak]

reverted height and width back to jsPDF with PR #2007

[jlahare]

Is this issue fixed ? is new version released, i m getting page width/height as undefined issue in 1.4.1 !!

[Uzlopak]

No. Will be released with 1.4.2

[Anderman]

How do I get intellisense in vscode? the types/jsPdf is outdated

[PCASME]

How do I get intellisense in vscode? the types/jsPdf is outdated

This is the main issue addressed here.
The types are not created/mantained in this repo nor by its contributors.
Hope the types generation will be included in the future in the build pipeline.

[Anderman]

I looked to this tsd-jsdoc
But I don't know how to run this with jspdf