There are several env vars that control how Deno behaves:

    defaults to $HOME/.cache/deno but can be set to any path to control where generated and cached source code is written and read to.

    NO_COLOR will turn off color output if set. See . User code can test if NO_COLOR was set without having --allow-env by using the boolean constant Deno.noColor.

    You can generate completion script for your shell using the deno completions <shell> command. The command outputs to stdout so you should redirect it to an appropriate file.

    The supported shells are:

    • zsh
    • bash
    • fish
    • powershell
    • elvish

    Example (bash):

    Example (zsh without framework):

    1. mkdir ~/.zsh # create a folder to save your completions. it can be anywhere

    then add this to your .zshrc

    1. fpath=(~/.zsh $fpath)
    2. autoload -Uz compinit
    3. compinit -u

    and restart your terminal. note that if completions are still not loading, you may need to run rm ~/.zcompdump/ to remove previously generated completions and then compinit to generate them again.

    After this add deno plugin under plugins tag in ~/.zshrc file. for tools like antigen path will be ~/.antigen/bundles/robbyrussell/oh-my-zsh/plugins and command will be antigen bundle deno and so on.

    Example (Powershell):

    1. deno completions powershell > $profile
    2. .$profile

    This will be create a Powershell profile at $HOME\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 by default, and it will be run whenever you launch the PowerShell.

    Because Deno requires the use of file extensions for module imports and allows http imports, and most editors and language servers do not natively support this at the moment, many editors will throw errors about being unable to find files or imports having unnecessary file extensions.

    The community has developed extensions for some editors to solve these issues:

    VS Code

    The beta version of is published on the Visual Studio Marketplace. Please report any issues.

    JetBrains IDEs

    Support for JetBrains IDEs is available through the Deno plugin.

    For more information on how to set-up your JetBrains IDE for Deno, read on YouTrack.

    Vim and NeoVim

    Vim works fairly well for Deno/TypeScript if you install (intellisense engine and language server protocol) or ALE (syntax checker and language server protocol client).

    CoC
    ALE

    ALE integrates with Deno’s LSP out of the box and should not require any extra configuration. However, if your Deno executable is not located in $PATH, has a different name than deno or you want to use unstable features/APIs, you need to override ALE’s default values. See .

    ALE provides support for autocompletion, refactoring, going to definition, finding references and more, however, key bindings need to be configured manually. Copy the snippet below into your vimrc/init.vim for basic configuration or consult the official documentation for a more in-depth look at how to configure ALE.

    ALE can fix linter issues by running deno fmt. To instruct ALE to use the Deno formatter the ale_linter setting needs to be set either on a per buffer basis (let b:ale_linter = ['deno']) or globally for all TypeScript files (let g:ale_fixers={'typescript': ['deno']})

    1. " Use ALE autocompletion with Vim's 'omnifunc' setting (press <C-x><C-o> in insert mode)
    2. autocmd FileType typescript set omnifunc=ale#completion#OmniFunc
    4. " Make sure to use map instead of noremap when using a <Plug>(...) expression as the {rhs}
    5. nmap gr <Plug>(ale_rename)
    6. nmap gR <Plug>(ale_find_reference)
    7. nmap gd <Plug>(ale_go_to_definition)
    8. nmap gD <Plug>(ale_go_to_type_definition)
    10. let g:ale_fixers = {'typescript': ['deno']}
    11. let g:ale_fix_on_save = 1 " run deno fmt when saving a buffer

    Emacs

    Emacs works pretty well for a TypeScript project targeted to Deno by using a combination of tide which is the canonical way of using TypeScript within Emacs and which is what is used by the official VSCode extension for Deno.

    To use it, first make sure that tide is setup for your instance of Emacs. Next, as instructed on the page, first npm install --save-dev typescript-deno-plugin typescript in your project (npm init -y as necessary), then add the following block to your tsconfig.json and you are off to the races!

    LSP clients

    Deno has builtin support for the as of version 1.6.0 or later.

    If your editor supports the LSP, you can use Deno as a language server for TypeScript and JavaScript.

    The editor can start the server with deno lsp.

    Example for Kakoune

    After installing the LSP client you can add the Deno language server by adding the following to your kak-lsp.toml

    1. [language.deno]
    2. filetypes = ["typescript", "javascript"]
    3. roots = [".git"]
    4. args = ["lsp"]
    Example for Vim/Neovim
    1. if executable("deno")
    2.   augroup LspTypeScript
    3.     autocmd!
    4.     autocmd User lsp_setup call lsp#register_server({
    5.     \ "name": "deno lsp",
    6.     \ "cmd": {server_info -> ["deno", "lsp"]},
    7.     \ "root_uri": {server_info->lsp#utils#path_to_uri(lsp#utils#find_nearest_parent_file_directory(lsp#utils#get_buffer_path(), "tsconfig.json"))},
    8.     \ "allowlist": ["typescript", "typescript.tsx"],
    9.     \ "initialization_options": {
    10.     \     "enable": v:true,
    11.     \     "lint": v:true,
    12.     \     "unstable": v:true,
    13.     \   },
    14.     \ })
    15.   augroup END
    16. endif
    Example for Sublime Text

    If you don’t see your favorite IDE on this list, maybe you can develop an extension. Our community Discord group can give you some pointers on where to get started.