diff options
author | Kitson Kelly <me@kitsonkelly.com> | 2021-07-18 16:30:17 +1000 |
---|---|---|
committer | GitHub <noreply@github.com> | 2021-07-18 16:30:17 +1000 |
commit | 44084cd0f925fb9972a0a0aafa1d2197e689f938 (patch) | |
tree | 972a512a5ae7f59013bb9e95019489b79ec5a9f8 /docs/typescript/overview.md | |
parent | e0e26b41016c5bf49f358ce7a285192159599306 (diff) |
docs: add npm-Node.js chapter (#11419)
Co-authored-by: Bartek IwaĆczuk <biwanczuk@gmail.com>
Diffstat (limited to 'docs/typescript/overview.md')
-rw-r--r-- | docs/typescript/overview.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/typescript/overview.md b/docs/typescript/overview.md index dbf0c9286..038ea35b1 100644 --- a/docs/typescript/overview.md +++ b/docs/typescript/overview.md @@ -152,8 +152,8 @@ bypass type checking all together. ### Type resolution -One of the core design principles of Deno is to avoid "magical" resolution, and -this applies to type resolution as well. If you want to utilise JavaScript that -has type definitions (e.g. a `.d.ts` file), you have to explicitly tell Deno -about this. The details of how this is accomplished are covered in the -[Types and type declarations](./types.md) section. +One of the core design principles of Deno is to avoid non-standard module +resolution, and this applies to type resolution as well. If you want to utilise +JavaScript that has type definitions (e.g. a `.d.ts` file), you have to +explicitly tell Deno about this. The details of how this is accomplished are +covered in the [Types and type declarations](./types.md) section. |