The registry of type definitions for TypeScript
The registry of type definitions for TypeScript.
You can create typings and distribute them with your NPM package. Check out how we can collaborate (if you need help) in this issue. The TypeScript team gives some additional help in their handbook, which entails creating a definition in external module format and linking to it from
package.json. Feel free to ask questions!
You can open an issue in the package's repository and ask if they'd be interested in providing a TypeScript definition for their users. If they are, you can link them to this issue on collaborating, in case they need a hand getting started.
npm testto check that the registry is valid, make a pull request
typings install debug
typings requestin the issues
types, see #480 so we can collaborate
typed-to differentiate from your other projects)
main(and other valid options)
The registry uses subdirectories to denote "sources". These sources are essentially mappings to package managers, and contain either ambient or external module typings (depending on the "source").
Where "source" is one of:
And "name" is the name of the package from the source. For GitHub and scoped NPM packages, it's valid to make a folder such as
@example/entry.json. The schema for package files is described using JSON schema in
For typings issues, questions or general help, you can always open an issue in the discussions repo. To add an entry to the registry, please open a pull request with the change.