Reference
Editor setup for type-checked JavaScript
Most editors run TypeScript's language service for JavaScript, either built in or through a language server, and it runs the same checker as tsc. These pages cover the settings that make the editor agree with your npm run lint: which TypeScript it runs, how it finds jsconfig.json, and how to see errors in files you have not opened.
All editors
-
VS Code
Set up VS Code for type-checked JavaScript: how it reads jsconfig.json, using the project's TypeScript version, and listing errors in files you have not opened.
- No extension needed
-
WebStorm
Type-checked JavaScript in WebStorm: the TypeScript version setting, the language service, project-wide errors, and how to confirm the IDE agrees with tsc.
- Built in
-
Neovim
Set up Neovim for type-checked JavaScript: vim.lsp.enable with ts_ls or vtsls, making the server use your project's TypeScript, and checking it agrees with tsc.
- nvim-lspconfig + a language server
-
Vim with ALE
Set up Vim with ALE for type-checked JavaScript: the tsserver linter, the project root ALE needs, the project's TypeScript, and checking it agrees with tsc.
- ALE plugin
-
Zed
Set up Zed for type-checked JavaScript: the vtsls server it uses by default, making it run your project's TypeScript, and checking it agrees with tsc.
- Built in
-
Sublime Text
Set up Sublime Text for type-checked JavaScript with the LSP and LSP-typescript packages: the server, its settings, and checking it agrees with tsc.
- LSP + LSP-typescript packages
-
Emacs
Set up Emacs for type-checked JavaScript with Eglot or lsp-mode and typescript-language-server: starting the server, picking its TypeScript, and matching tsc.
- Eglot (built in) or lsp-mode
-
Helix
Set up Helix for type-checked JavaScript: the typescript-language-server it uses by default, its jsconfig.json root detection, and checking it agrees with tsc.
- typescript-language-server