Remove the unofficial TypeScript definitions from DefinitelyTyped

Currently there’s unofficial, likely unmaintained, and out-of-date TypeScript definitions published via https://github.com/DefinitelyTyped/DefinitelyTyped for the pdfjs-dist library; see https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/pdfjs-dist

Now that we, from version 2.6.347, are shipping official TypeScript definitions through https://github.com/mozilla/pdfjs-dist, it’d be a good idea to submit a PR to DefinitelyTyped to remove its TypeScript definitions; see https://github.com/DefinitelyTyped/DefinitelyTyped#removing-a-package

[tamuratak]

For PDF.js v2.6.347, you can import them with the following:

import type {PDFDocumentProxy, PDFPageProxy} from 'pdfjs-dist/types/display/api'

[billyjanitsch]

The official TS definitions bundled in 2.6.347, while much appreciated, only include bindings for the top-level API and therefore lack many of the useful types currently exposed by the DefinitelyTyped definitions, such as:

• PDFPageProxy
• PDFDocumentProxy
• PDFRenderTask
• PDFDocumentLoadingTask

It’s possible to access these types through the official definitions by using complex sequences of type operations, e.g.:

type PDFDocumentProxyPromise = ReturnType<typeof getDocument>['promise']
type PDFDocumentProxy = PDFDocumentProxyPromise extends Promise<infer U> ? U : never

However, this is inconvenient and also unconventional within the TypeScript ecosystem. Type definitions for libraries usually export typings for important objects/classes (without exporting their values).

Would you consider exposing these types in the official type definitions before removing the typings from DefinitelyTyped?