docs: update JetBrains environment support (#5877)

denoland · May 26, 2020 · d4711fe · d4711fe
1 parent 845bc44
commit d4711fe
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 5 deletions.
diff --git a/docs/getting_started/setup_your_environment.md b/docs/getting_started/setup_your_environment.md
@@ -54,12 +54,12 @@ Please report any issues.
 
 #### JetBrains IDEs
 
-Support for JetBrains IDEs is not yet available, but you can follow and upvote
-these issues to stay up to date:
+Support for JetBrains IDEs is available through
+[the Deno plugin](https://plugins.jetbrains.com/plugin/14382-deno).
 
-- https://youtrack.jetbrains.com/issue/WEB-41607
-- https://youtrack.jetbrains.com/issue/WEB-42983
-- https://youtrack.jetbrains.com/issue/WEB-31667
+For more information on how to set-up your JetBrains IDE for Deno, read
+[this comment](https://youtrack.jetbrains.com/issue/WEB-41607#focus=streamItem-27-4160152.0-0)
+on YouTrack.
 
 #### Vim and NeoVim
 

diff --git a/docs/tools/debugger.md b/docs/tools/debugger.md
@@ -122,6 +122,14 @@ Change `<entry_point>` to `server.ts` and run created configuration:
 
 ![VSCode debugger](../images/debugger7.jpg)
 
+### JetBrains IDEs
+
+You can debug Deno using your JetBrains IDE by right-clicking the file you want
+to debug and selecting the `Debug 'Deno: <file name>'` option. This will create
+a run/debug configuration which has no permission flags set, so to change that
+you need to modify the run/debug configuration and change the `Arguments` field
+with the required flags.
+
 ### Other
 
 Any client that implements Devtools protocol should be able to connect to Deno