Need help with DefinitelyTyped?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

36.3K Stars 26.0K Forks Other 78.0K Commits 767 Opened issues


The repository for high quality TypeScript type definitions.

Services available


Need anything else?

Contributors list

Definitely Typed

The repository for high quality TypeScript type definitions.

You can also read this README in Spanish, Korean, Russian, Chinese, Portuguese, Italian and Japanese!

Link to Admin manual

Current status

This section tracks the health of the repository and publishing process. It may be helpful for contributors experiencing any issues with their PRs and packages.

If anything here seems wrong, or any of the above are failing, please let us know in the Definitely Typed channel on the TypeScript Community Discord server.

What are declaration files and how do I get them?

See the TypeScript handbook.


This is the preferred method. For example:

npm install --save-dev @types/node

The types should then be automatically included by the compiler. You may need to add a

reference if you're not using modules:

See more in the handbook.

For an npm package "foo", typings for it will be at "@types/foo". If you can't find your package, look for it on TypeSearch.

If you still can't find it, check if it bundles its own typings. This is usually provided in a

field in the
, or just look for any ".d.ts" files in the package and manually include them with a

Support Window

Definitely Typed only tests packages on versions of TypeScript that are less than 2 years old.

Currently versions 3.7 and above are tested...

If you're using TypeScript 2.0 to 3.6, you can still try installing @types packages — the majority of packages don't use fancy new TypeScript features. But there's no guarantee that they'll work. Here is the support window:

Version Released End of Support
2.8 March 2018 March 2020
2.9 May 2018 May 2020
3.0 July 2018 August 2020
3.1 September 2018 September 2020
3.2 November 2018 November 2020
3.3 January 2019 January 2021
3.4 March 2019 March 2021
3.5 May 2019 May 2021
3.6 August 2019 August 2021
3.7 November 2019 November 2021
3.8 February 2020 February 2022
3.9 May 2020 May 2022
4.0 August 2020 August 2022
4.1 November 2020 November 2022
4.2 February 2021 February 2023
4.3 May 2021 May 2023
4.4 August 2021 August 2023

@types packages have tags for versions of TypeScript that they explicitly support, so you can usually get older versions of packages that predate the 2-year window. For example, if you run npm dist-tags @types/react, you'll see that TypeScript 2.5 can use types for [email protected], whereas TypeScript 2.6 and 2.7 can use types for [email protected]:

Tag Version
latest 16.9.23
ts2.0 15.0.1
... ...
ts2.5 16.0.36
ts2.6 16.4.7
ts2.7 16.4.7
... ...

TypeScript 1.*

  • Manually download from the master branch of this repository and place them in your project
  • Typings (use preferred alternatives, typings is deprecated)
  • NuGet (use preferred alternatives, nuget DT type publishing has been turned off)

You may need to add manual references.

How can I contribute?

Definitely Typed only works because of contributions by users like you!


Before you share your improvement with the world, use the types yourself by creating a

file in your project and filling out its exports:
declare module "libname" { 
  // Types inside here
  export function helloWorldMessage(): string

Test editing an existing package

You can edit the types directly in

to validate your changes, then bring the changes to this repo with the steps below.

Alternatively, you can use module augmentation to extend existing types from the DT module or use the

declare module
technique above which will override the version in

Adding tests to a new package

Add to your

"baseUrl": "types",
"typeRoots": ["types"],


containing declarations for the module "foo". You should now be able to import from
in your code and it will route to the new type definition. Then build and run the code to make sure your type definition actually corresponds to what happens at runtime.

Once you've tested your definitions with real code, make a PR then follow the instructions to edit an existing package or create a new package.

Make a pull request

Once you've tested your package, you can share it on Definitely Typed.

First, fork this repository, clone it, install node, and run

npm install
. If using
v7 you need to add the
flag to the command.

We use a bot to let a large number of pull requests to DefinitelyTyped be handled entirely in a self-service manner. You can read more about why and how here. Here is a handy reference showing the life-cycle of a pull request to DT:

Partial clone

You can clone the entire repository as per usual, but it's large and includes a massive directory of type packages.

You can clone the entire repository as per usual, but it's large and includes a massive directory of type packages. This will take some time to clone and may be unnecessarily unwieldy.

For a more manageable clone that includes only the type packages relevant to you, you can use git's sparse-checkout, --filter, and --depth features. This will reduce clone time and improve git performance.

>:warning: This requires minimum git version 2.27.0, which is likely newer than the default on most machines. More complicated procedures are available in older versions, but not covered by this guide.

  1. git clone --sparse --filter=blob:none --depth=1 <forkedurl>
    • --sparse initializes the sparse-checkout file so the working directory starts with only the files in the root of the repository.
    • --filter=blob:none will exclude files, fetching them only as needed.
    • --depth=1 will further improve clone speed by truncating commit history, but it may cause issues as summarized here.
  2. git sparse-checkout add types/<type> types/<dependency-type> ...

Edit an existing package

When you make a PR to edit an existing package,

should @-mention previous authors. If it doesn't, you can do so yourself in the comment associated with the PR.

Create a new package

If you are the library author and your package is written in TypeScript, bundle the autogenerated declaration files in your package instead of publishing to Definitely Typed.

If you are adding typings for an npm package, create a directory with the same name. If the package you are adding typings for is not on npm, make sure the name you choose for it does not conflict with the name of a package on npm. (You can use

npm info 
to check for the existence of the

Your package should have this structure:

| File | Purpose | | ------------- | ------- | |

| This contains the typings for the package. | |
| This contains sample code which tests the typings. This code does not run, but it is type-checked. | |
| This allows you to run
within the package. | |
| Enables linting. |

Generate these by running

npx dts-gen --dt --name  --template module
if you have npm ≥ 5.2.0,
npm install -g dts-gen
dts-gen --dt --name  --template module
otherwise. See all options at dts-gen.

If you have

files besides
, make sure that they are referenced either in
or the tests.

Definitely Typed members routinely monitor for new PRs, though keep in mind that the number of other PRs may slow things down.

For a good example package, see base64-js.

Removing a package

When a package bundles its own types, types should be removed from Definitely Typed to avoid confusion.

You can remove it by running

npm run not-needed --   []
. *
: This is the name of the directory to delete.
: A stub will be published to 
with this version. Should be higher than any currently published version, and should be a version of
 on npm.
: Name of npm package that replaces the Definitely Typed types. Usually this is identical to 
, in which case you can omit it.

Any other packages in Definitely Typed that referenced the deleted package should be updated to reference the bundled types. You can get this list by looking at the errors from

npm run test-all
. To fix the errors, add a
"dependencies": { "": "x.y.z" }
. For example:
  "private": true,
  "dependencies": {
    "": "^2.6.0"

When you add a

to dependents of
, you will also need to open a PR to add 
 to allowedPackageJsonDependencies.txt in DefinitelyTyped-tools.

If a package was never on Definitely Typed, it does not need to be added to


Running tests

Test your changes by running

npm test 
 is the name of your package.

This script uses dtslint to run the TypeScript compiler against your dts files.

Once you have all your changes ready, use

npm run test-all
to see how your changes affect other modules.


If you are adding typings for an npm package, create a directory with the same name. If the package you are adding typings for is not on npm, make sure the name you choose for it does not conflict with the name of a package on npm. (You can use

npm info 
to check for the existence of the

If a non-npm package conflicts with an existing npm package try adding -browser to the end of the name to get



There should be a

file, which is considered your test file, along with any
files it imports. If you don't see any test files in the module's folder, create a
. These files are used to validate the API exported from the
files which are shipped as

Changes to the

files should include a corresponding
file change which shows the API being used, so that someone doesn't accidentally break code you depend on. If you don't see any test files in the module's folder, create a

For example, this change to a function in a

file adding a new param to a function:

- export function twoslash(body: string): string
+ export function twoslash(body: string, config?: { version: string }): string

import {twoslash} from "./"

// $ExpectType string const result = twoslash("//")

  • // Handle options param
  • const resultWithOptions = twoslash("//", { version: "3.7" })
  • // When the param is incorrect
  • // $ExpectError
  • const resultWithOptions = twoslash("//", { })

If you're wondering where to start with test code, the examples in the README of the module are a great place to start.

You can validate your changes with

npm test 
from the root of this repo, which takes changed files into account.


to assert that an expression is of a given type, and
to assert that a compile error. Examples:
// $ExpectType void

// $ExpectError f("one");

For more details, see dtslint readme.


The linter configuration file,

should contain
{ "extends": "dtslint/dt.json" }
, and no additional rules.

If for some reason some rule needs to be disabled, disable it for that specific line using

// tslint:disable-next-line:[ruleName]
— not for the whole package, so that disabling can be reviewed. (There are some legacy lint configs that have additional contents, but these should not happen in new work.)


should have
, and
set to

You may edit the

to add new test files, to add
"target": "es6"
(needed for async functions), to add to
, or to add the
compiler option.


are not allowed in your

These options make it possible to write a default import for a CJS export, modeling the built-in interoperability between CJS and ES modules in Node and in some JS bundlers:

// component.d.ts
declare class Component {​​​​​}​​​​​
// CJS export, modeling `module.exports = Component` in JS
export = Component;

// index.d.ts // ESM default import, only allowed under 'esModuleInterop' or 'allowSyntheticDefaultExports' import Component from "./component";

Since the compile-time validity of the import in

is dependent upon specific compilation settings, which users of your types do not inherit, using this pattern in DefinitelyTyped would force users to change their own compilation settings, which might be incorrect for their runtime. Instead, you must write a CJS import for a CJS export to ensure widespread, config-independent compatibility:
// index.d.ts
// CJS import, modeling `const Component = require("./component")` in JS
import Component = require("./component");


Usually you won't need this. DefinitelyTyped's package publisher creates a

for packages with no dependencies outside Definitely Typed. A
may be included to specify dependencies that are not other
packages. Pikaday is a good example. Even if you write your own
, you can only specify dependencies; other fields such as
are not allowed. You also need to add the dependency to the list of allowed packages. This list is updated by a human, which gives us the chance to make sure that
packages don't depend on malicious packages.

In the rare case that an

package is deleted and removed in favor of types shipped by the source package AND you need to depend on the old, removed
package, you can add a dependency on an
package. Be sure to explain this when adding to the list of allowed packages so that the human maintainer knows what is happening.


If a file is neither tested nor referenced in

, add it to a file named
. This file is a list of other files that need to be included in the typings package, one file per line.

Common mistakes

  • First, follow advice from the handbook.
  • Formatting: Use 4 spaces. Prettier is set up on this repo, so you can run
    npm run prettier -- --write path/to/package/**/*.ts
    . When using assertions, add
    // prettier-ignore
    exclusion to mark line(s) of code as excluded from formatting:
    // prettier-ignore
    const incompleteThemeColorModes: Theme = { colors: { modes: { papaya: { // $ExpectError
  • function sum(nums: number[]): number
    : Use
    if a function does not write to its parameters.
  • interface Foo { new(): Foo; }
    : This defines a type of objects that are new-able. You probably want
    declare class Foo { constructor(); }
  • const Class: { new(): IClass; }
    : Prefer to use a class declaration
    class Class { constructor(); }
    instead of a new-able constant.
  • getMeAT(): T
    : If a type parameter does not appear in the types of any parameters, you don't really have a generic function, you just have a disguised type assertion. Prefer to use a real type assertion, e.g.
    getMeAT() as number
    . Example where a type parameter is acceptable:
    function id(value: T): T;
    . Example where it is not acceptable:
    function parseJson(json: string): T;
    . Exception:
    new Map()
    is OK.
  • Using the types
    is almost never a good idea. In 99% of cases it's possible to specify a more specific type. Examples are
    (x: number) => number
    for functions and
    { x: number, y: number }
    for objects. If there is no certainty at all about the type,
    is the right choice, not
    . If the only known fact about the type is that it's some object, use the type
    , not
    { [key: string]: any }
  • var foo: string | any
    : When
    is used in a union type, the resulting type is still
    . So while the
    portion of this type annotation may look useful, it in fact offers no additional typechecking over simply using
    . Depending on the intention, acceptable alternatives could be
    , or
    string | object

Definition owners

TL;DR: do not modify

, always modify list of the owners in the

DT has the concept of "Definition Owners" which are people who want to maintain the quality of a particular module's types

  • Adding yourself to the list will cause you to be notified (via your GitHub username) whenever someone makes a pull request or issue about the package.
  • Your PR reviews will have a higher precedence of importance to the bot which maintains this repo.
  • The DT maintainers are putting trust in the definition owners to ensure a stable eco-system, please don't add yourself lightly.

To Add yourself as a Definition Owner:

  • Adding your name to the end of the line, as in
    // Definitions by: Alice , Bob 
  • Or if there are more people, it can be multiline
    // Definitions by: Alice 
    //                 Bob 
    //                 Steve 
    //                 John 

Once a week the Definition Owners are synced to the file .github/CODEOWNERS which is our source of truth.


What exactly is the relationship between this repository and the
packages on npm?


branch is automatically published to the
scope on npm thanks to DefinitelyTyped-tools.

I've submitted a pull request. How long until it is merged?

It depends, but most pull requests will be merged within a week. Some PRs can be merged by the owners of a module, and they can be merged much faster. Roughly:

PRs which only change the types of a module, and have corresponding tests changes will be merged much faster

PRs that have been approved by an author listed in the definition's header are usually merged more quickly; PRs for new definitions will take more time as they require more review from maintainers. Each PR is reviewed by a TypeScript or Definitely Typed team member before being merged, so please be patient as human factors may cause delays. Check the New Pull Request Status Board to see progress as maintainers work through the open PRs.

I'd like to submit a change to a very popular project, why are they treated differently?

For changes to very popular modules, e.g. Node/Express/Jest which have many millions of downloads each per week on npm, the requirements for contributions are a bit higher. Changes to these projects can have massive ecosystem effects, and so we treat changes to the with a lot of care. These modules require both a sign-off from a DT maintainer, and enthusiastic support from the module owners. The bar for passing this can be quite high, and often PRs can go stale because it doesn't have a champion. If you're finding that no-one is committing, try to make your PR have a smaller focus.

My PR is merged; when will the
npm package be updated?

npm packages should update within a few minutes. If it's been more than an hour, mention the PR number on the Definitely Typed channel on the TypeScript Community Discord server and the current maintainer will get the correct team member to investigate.

I'm writing a definition that depends on another definition. Should I use
 or an import?

If the module you're referencing is an external module (uses

), use an import. If the module you're referencing is an ambient module (uses
declare module
, or just declares globals), use

Some packages have no
, and some
are missing
"noImplicitAny": true
"noImplicitThis": true
, or
"strictNullChecks": true

Then they are wrong, and we've not noticed yet. You can help by submitting a pull request to fix them.

Can I change/enforce formatting settings for modules?

No. We've explored trying to make DT's code-formatting consistent before but reached an impasse due to the high activity on the repo. We include formatting settings via a

. These are exclusively for tooling in your editor, their settings don't conflict and we don't plan on changing them. Nor do we plan on enforcing a specific style in the repo. We want to keep the barriers to contributions low.

Can I request a definition?

Here are the currently requested definitions.

What about type definitions for the DOM?

If types are part of a web standard, they should be contributed to TypeScript-DOM-lib-generator so that they can become part of the default


Should I add an empty namespace to a package that doesn't export a module to use ES6 style imports?

Some packages, like chai-http, export a function.

Importing this module with an ES6 style import in the form

import * as foo from "foo";
leads to the error:

error TS2497: Module 'foo' resolves to a non-module entity and cannot be imported using this construct

This error can be suppressed by merging the function declaration with an empty namespace of the same name, but this practice is discouraged. This is a commonly cited Stack Overflow answer regarding this matter.

It is more appropriate to import the module using the

import foo = require("foo");
syntax. Nevertheless, if you want to use a default import like
import foo from "foo";
you have two options: - you can use the
compiler option
if your module runtime supports an interop scheme for non-ECMAScript modules, i.e. if default imports work in your environment (e.g. Webpack, SystemJS, esm). - you can use the
compiler option
if you want TypeScript to take care of non-ECMAScript interop (since TypeScript 2.7).

A package uses
export =
, but I prefer to use default imports. Can I change
export =
export default

Like in the previous question, refer to using either the

compiler options.

Do not change the type definition if it is accurate. For an npm package,

export =
is accurate if
node -p 'require("foo")'
works to import a module, and
export default
is accurate if
node -p 'require("foo").default'
works to import a module.

I want to use features from very new TypeScript versions.

Then you will have to add a comment to the last line of your definition header (after

// Definitions:
// Minimum TypeScript Version: X.Y
. This will set the lowest minimum supported version.

However, if your project needs to maintain types that are compatible with, say, 3.7 and above at the same time as types that are compatible with 3.6 or below, you will need to use the

feature. You can find a detailed explanation of this feature in the official TypeScript documentation.

Here's a short example to get you started:

  1. You'll have to add a
    file to your package definition, with the following contents:
     "private": true,
     "types": "index",
     "typesVersions": {
       "<=3.6": { "*": ["ts3.6/*"] }
  1. Create the sub-directory mentioned in the
    field inside your types directory (
    in this example).
    will support TypeScript versions 3.6 and below, so copy the existing types and tests there.

You'll need to delete the definition header from

since only the root
is supposed to have it.
  1. Set the

    options in
    to the correct paths, which should look something like this:
     "compilerOptions": {
       "baseUrl": "../../",
       "typeRoots": ["../../"]
  2. Back in the root of the package, add the TypeScript 3.7 features you want to use. When people install the package, TypeScript 3.6 and below will start from

    , whereas TypeScript 3.7 and above will start from

You can look at bluebird for an example.

I want to add a DOM API not present in TypeScript by default.

This may belong in TypeScript-DOM-lib-generator. See the guidelines there. If the standard is still a draft, it belongs here. Use a name beginning with

and include a link to the standard as the "Project" link in the header. When it graduates draft mode, we may remove it from Definitely Typed and deprecate the associated

How do Definitely Typed package versions relate to versions of the corresponding library?

NOTE: The discussion in this section assumes familiarity with Semantic versioning

Each Definitely Typed package is versioned when published to npm. The DefinitelyTyped-tools (the tool that publishes

packages to npm) will set the declaration package's version by using the
version number listed in the first line of its
file. For example, here are the first few lines of Node's type declarations for version
at the time of writing:
// Type definitions for Node.js 10.12
// Project:
// Definitions by: Microsoft TypeScript 
//                 Definitely Typed 
//                 Alberto Schiabel 


is at the end of the first line, the npm version of the
package will also be
. Note that the first-line comment in the
file should only contain the
version (e.g.
) and should not contain a patch version (e.g.
). This is because only the major and minor release numbers are aligned between library packages and type declaration packages. The patch release number of the type declaration package (e.g.
) is initialized to zero by Definitely Typed and is incremented each time a new
package is published to npm for the same major/minor version of the corresponding library.

Sometimes type declaration package versions and library package versions can get out of sync. Below are a few common reasons why, in order of how much they inconvenience users of a library. Only the last case is typically problematic.

  • As noted above, the patch version of the type declaration package is unrelated to the library patch version. This allows Definitely Typed to safely update type declarations for the same major/minor version of a library.
  • If updating a package for new functionality, don't forget to update the version number to line up with that version of the library. If users make sure versions correspond between JavaScript packages and their respective
    packages, then
    npm update
    should typically just work.
  • It's common for type declaration package updates to lag behind library updates because it's often library users, not maintainers, who update Definitely Typed when new library features are released. So there may be a lag of days, weeks, or even months before a helpful community member sends a PR to update the type declaration package for a new library release. If you're impacted by this, you can be the change you want to see in the world and you can be that helpful community member!

:exclamation: If you're updating type declarations for a library, always set the

version in the first line of
to match the library version that you're documenting! :exclamation:

If a library is updated to a new major version with breaking changes, how should I update its type declaration package?

Semantic versioning requires that versions with breaking changes must increment the major version number. For example, a library that removes a publicly exported function after its

release must bump its version to
in its next release. Furthermore, when the library's
release is out, its Definitely Typed type declaration package should also be updated to
, including any breaking changes to the library's API.

Many libraries have a large installed base of developers (including maintainers of other packages using that library as a dependency) who won't move right away to a new version that has breaking changes, because it might be months until a maintainer has time to rewrite code to adapt to the new version. In the meantime, users of old library versions still may want to update type declarations for older versions.

If you intend to continue updating the older version of a library's type declarations, you may create a new subfolder (e.g.

) named for the current (soon to be "old") version, and copy existing files from the current version to it.

Because the root folder should always contain the type declarations for the latest ("new") version, you'll need to make a few changes to the files in your old-version subdirectory to ensure that relative path references point to the subdirectory, not the root.

  1. Update the relative paths in
    as well as
  2. Add path mapping rules to ensure that tests are running against the intended version.

For example, the

library introduced breaking changes between version

. Because many users still consumed the older
version, a maintainer who wanted to update the type declarations for this library to
added a
folder inside the history repository that contains type declarations for the older version. At the time of writing, the history v2
looks roughly like:
  "compilerOptions": {
    "baseUrl": "../../",
    "typeRoots": ["../../"],
    "paths": {
      "history": [ "history/v2" ]
  "files": [

If there are other packages in Definitely Typed that are incompatible with the new version, you will need to add path mappings to the old version. You will also need to do this recursively for packages depending on the old version.

For example,

depends on
[email protected]
, so react-router
has a path mapping to
"history": [ "history/v2" ]
. Transitively,
(which depends on
) also needed to add the same path mapping (
"history": [ "history/v2" ]
) in its
until its
dependency was updated to the latest version.


will not work with path mapping, so dependencies must use

How do I write definitions for packages that can be used globally and as a module?

The TypeScript handbook contains excellent general information about writing definitions, and also this example definition file which shows how to create a definition using ES6-style module syntax, while also specifying objects made available to the global scope. This technique is demonstrated practically in the definition for

, which is a library that can be loaded globally via script tag on a web page, or imported via require or ES6-style imports.

To test how your definition can be used both when referenced globally or as an imported module, create a

folder, and place two test files in there. Name one
and the other
. The global test file should exercise the definition according to how it would be used in a script loaded on a web page where the library is available on the global scope - in this scenario you should not specify an import statement. The module test file should exercise the definition according to how it would be used when imported (including the
statement(s)). If you specify a
property in your
file, be sure to include both test files. A practical example of this is also available on the

Please note that it is not required to fully exercise the definition in each test file - it is sufficient to test only the globally-accessible elements on the global test file and fully exercise the definition in the module test file, or vice versa.

What about scoped packages?

Types for a scoped package

should go in
. Note the double underscore.


is used to scaffold a scoped package, the
property has to be manually adapted in the generated
to correctly reference the scoped package:
  "paths": {
    "@foo/*": ["foo__*"]

The file history in GitHub looks incomplete.

GitHub doesn't support file history for renamed files. Use

git log --follow


This project is licensed under the MIT license.

Copyrights on the definition files are respective of each contributor listed at the beginning of each definition file.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.