summaryrefslogtreecommitdiff
path: root/docs/typescript
diff options
context:
space:
mode:
Diffstat (limited to 'docs/typescript')
-rw-r--r--docs/typescript/faqs.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/typescript/faqs.md b/docs/typescript/faqs.md
index 65f1d92b7..3b5b7e0b1 100644
--- a/docs/typescript/faqs.md
+++ b/docs/typescript/faqs.md
@@ -114,3 +114,16 @@ compiler. Its main purpose is to ensure that TypeScript and JavaScript can run
under Deno. The secondary ability to do TypeScript and JavaScript emitting via
the runtime API `Deno.emit()` is intended to be simple and straight forward and
support a certain set of use cases.
+
+### How do I combine Deno code with non-Deno code in my IDE?
+
+The Deno language server supports the ability to have a "per-resource"
+configuration of enabling Deno or not. This also requires a client IDE to
+support this ability. For Visual Studio Code the official
+[Deno extension](https://marketplace.visualstudio.com/items?itemName=denoland.vscode-deno)
+supports the vscode concept of
+[multi-root workspace](https://code.visualstudio.com/docs/editor/multi-root-workspaces).
+This means you just need to add folders to the workspace and set the
+`deno.enable` setting as required on each folder.
+
+For other IDEs, the client extensions needs to support the similar IDE concepts.