summaryrefslogtreecommitdiff
path: root/docs/typescript/configuration.md
diff options
context:
space:
mode:
authorKitson Kelly <me@kitsonkelly.com>2021-06-22 07:18:32 +1000
committerGitHub <noreply@github.com>2021-06-22 07:18:32 +1000
commit281c4cd8fcf5fd54f558a6922736def2c7804529 (patch)
tree65ac91c5a41a64dc0b85ee9c5949d7086e8620ef /docs/typescript/configuration.md
parentcda15f2a98b10330422d1c8352d163d703ee6a49 (diff)
feat(cli): support "types" when type checking (#10999)
Fixes #10677
Diffstat (limited to 'docs/typescript/configuration.md')
-rw-r--r--docs/typescript/configuration.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/typescript/configuration.md b/docs/typescript/configuration.md
index ed5af56d7..752b6da71 100644
--- a/docs/typescript/configuration.md
+++ b/docs/typescript/configuration.md
@@ -197,3 +197,10 @@ The biggest "danger" when doing something like this, is that the type checking
is significantly looser, and there is no way to validate that you are doing
sufficient and effective feature detection in your code, which may lead to what
could be trivial errors becoming runtime errors.
+
+### Using the "types" property
+
+The `"types"` property in `"compilerOptions"` can be used to specify arbitrary
+type definitions to include when type checking a programme. For more information
+on this see
+[Using ambient or global types](./types#using-ambient-or-global-types).