diff options
Diffstat (limited to 'docs/typescript')
| -rw-r--r-- | docs/typescript/faqs.md | 8 | ||||
| -rw-r--r-- | docs/typescript/overview.md | 10 | ||||
| -rw-r--r-- | docs/typescript/types.md | 14 |
3 files changed, 16 insertions, 16 deletions
diff --git a/docs/typescript/faqs.md b/docs/typescript/faqs.md index 00bc99552..5db02cb7e 100644 --- a/docs/typescript/faqs.md +++ b/docs/typescript/faqs.md @@ -18,10 +18,10 @@ If you are using `tsc` as stand-alone, the setting to use is `"isolatedModules"` and setting it to `true` to help ensure that your code can be properly handled by Deno. -One of the ways to deal with the extension and the lack of _magical_ resolution -is to use [import maps](../linking_to_external_code/import_maps.md) which would -allow you to specify "packages" of bare specifiers which then Deno could resolve -and load. +One of the ways to deal with the extension and the lack of Node.js non-standard +resolution logic is to use +[import maps](../linking_to_external_code/import_maps.md) which would allow you +to specify "packages" of bare specifiers which then Deno could resolve and load. ### What version(s) of TypeScript does Deno support? 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. diff --git a/docs/typescript/types.md b/docs/typescript/types.md index ba5462dc7..02257ff3d 100644 --- a/docs/typescript/types.md +++ b/docs/typescript/types.md @@ -1,12 +1,12 @@ ## Types and Type Declarations -One of the design principles of Deno is no _magical_ resolution. When TypeScript -is type checking a file, it only cares about the types for the file, and the -`tsc` compiler has a lot of logic to try to resolve those types. By default, it -expects _ambiguous_ module specifiers with an extension, and will attempt to -look for the file under the `.ts` specifier, then `.d.ts`, and finally `.js` -(plus a whole other set of logic when the module resolution is set to `"node"`). -Deno deals with explicit specifiers. +One of the design principles of Deno is no non-standard module resolution. When +TypeScript is type checking a file, it only cares about the types for the file, +and the `tsc` compiler has a lot of logic to try to resolve those types. By +default, it expects _ambiguous_ module specifiers with an extension, and will +attempt to look for the file under the `.ts` specifier, then `.d.ts`, and +finally `.js` (plus a whole other set of logic when the module resolution is set +to `"node"`). Deno deals with explicit specifiers. This can cause a couple problems though. For example, let's say I want to consume a TypeScript file that has already been transpiled to JavaScript along |