From 44084cd0f925fb9972a0a0aafa1d2197e689f938 Mon Sep 17 00:00:00 2001 From: Kitson Kelly Date: Sun, 18 Jul 2021 16:30:17 +1000 Subject: docs: add npm-Node.js chapter (#11419) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Bartek Iwańczuk --- docs/typescript/overview.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/typescript/overview.md') 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. -- cgit v1.2.3