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/faqs.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/faqs.md')
-rw-r--r-- | docs/typescript/faqs.md | 8 |
1 files changed, 4 insertions, 4 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? |