Typescript definition file

[Bigous]

Could you include the d.ts file in this client distribution?

[isman-usoh]

+1

[panKt]

+1 👍

[robby-cornelissen]

+1

[christhomas]

yes absolutely! this project really needs a typescript definition file....

[robby-cornelissen]

I took a stab at generating Typescript definitions based on the endpoint data from Google's discovery API. Disclaimer: I'm fairly new to all things Node & Typescript. Caveat emptor. Anyhow, typings available in the dist folder: https://github.com/procrastinatos/google-api-nodejs-tsd

[Bigous]

It seams that with the new SALSA technology, typescript will be able to recognize things without .d.ts - there is a pull request enable this things.

[VamshiKrishnaAlladi]

+1

[arondesign]

+1

[n-sviridenko]

+1

[danieloprado]

+1

[masimplo]

Any news on this? Typings would greatly improve our experience working with this library.

[abruneau]

+1

[abruneau]

Since Typescript 2.1 you can import Untyped modules
So you can do
import * as google from "googleapis";

But for that, we need to update the package.json file and change main to "main": "./lib/googleapis.js",

[JustinBeckwith]

I'm starting to work on this one. This has to be done over several PRs, but the plan is:

• Perform a basic update the files to *.ts and wire up the compiler (First step to TypeScript upgrade #731)
• Introduce arrow functions, const, let, and other basics (Arrow functions, let/const, and cleanup #732)
• Fix syntax to move towards classes and es6 style imports
• Introduce tslint with relaxed configuration
• Add noImplicitAny to the tsconfig.json and apply required types
• Include the .d.ts file along with the npm module

Feedback on the approach welcomed.

[supermacro]

hey @JustinBeckwith any update on this? You also don't need a .d.ts file since the code is written in typescript. The typedefs should be baked into the code itself. Otherwise the simple fix would have been to leave all of the code as it was and simply include a .d.ts. file to describe the structure of the JS package to the ts compiler.

Axios is a good example of this approach.

[supermacro]

To add to the above comment: Despite the .ts file extensions, my compiler doesn't pick up any type information from this repo. Hence I'm forced to write my own googleapis.d.ts file in my project. Is there some configuration I need to do on my tsconfig in order to start inferring types from a typescript-based module?

[martywins]

@JustinBeckwith Any update on this? Super keen for these types.

[JustinBeckwith]

Apologies for the delay here folks. We did a lot of work to get things moved over to typescript, but I just haven't gone the last mile to get the generated d.ts included in the package. There's a PR over in #785 to cover this :)

[bjrnt]

@JustinBeckwith Looks like #785 been merged. Would be amazing to get a new version with this and the types field in package.json set! :)

[0x80]

@JustinBeckwith any news on this?

[oleg-codaio]

BUMP. Any news?

[JustinBeckwith]

Yes! We do ship a d.ts today. It's not terribly useful, because we don't have type information for the majority of the APIs. Most of the infrastructure is in place, but there's a lot of work left to generate better TypeScript for the libs.

[kaminskypavel]

the year is 2022... and we still have to define types manually. C'mon google we believe in you.. 😉

.