ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

LSP-typescript

by sublimelsp ST3

TypeScript, JavaScript support for Sublime LSP plugin

Details

  • 1.14.0
    1.9.1
  • github.​com
  • github.​com
  • 3 weeks ago
  • 3 hours ago
  • 3 years ago

Installs

  • Total 16K
  • Win 5K
  • Mac 6K
  • Linux 4K
Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5 Sep 4 Sep 3 Sep 2 Sep 1 Aug 31 Aug 30 Aug 29 Aug 28 Aug 27 Aug 26 Aug 25 Aug 24 Aug 23 Aug 22 Aug 21
Windows 4 11 11 9 11 9 13 11 9 26 7 8 13 12 12 6 9 15 9 10 17 12 13 11 9 12 11 13 9 13 17 8 5 16 12 12 8 12 6 5 11 16 15 11 13 7
Mac 7 14 16 12 7 13 22 14 15 8 8 8 15 14 22 9 7 11 13 23 18 16 18 16 9 6 19 17 16 12 11 12 15 23 13 13 16 19 8 11 13 17 15 28 17 5
Linux 4 9 13 6 9 15 11 14 9 12 7 15 9 7 11 13 15 13 5 13 9 11 13 9 16 8 9 9 9 11 8 8 10 13 9 14 8 15 10 13 6 13 8 12 14 9

Readme

Source
raw.​githubusercontent.​com

LSP-typescript

TypeScript and JavaScript support for Sublime's LSP plugin provided through TypeScript Language Server.

Installation

  • Install LSP and LSP-typescript from Package Control.
  • For ST4: The TypeScript and React (TSX) syntaxes are built-in so no need to install anything else.
  • For ST3: If you are working with TypeScript install TypeScript Syntax. If you are working with React install JSCustom.
  • Restart Sublime.

Configuration

Open the configuration file using the Command Palette Preferences: LSP-typescript Settings command or open it from the Sublime menu.

Organize Imports command

To sort or remove unused imports you can trigger the LSP-typescript: Organize Imports command from the Command Palette or create a key binding. For example:

{ "keys": ["ctrl+k"], "command": "lsp_execute",
        "args": {
            "session_name": "LSP-typescript",
            "command_name": "_typescript.organizeImports",
            "command_args": ["${file}"]
        }
    },

Code Actions on Save

The server supports the following code actions that can be specified in the global lsp_code_actions_on_save setting and run on saving files:

  • source.addMissingImports.ts - adds imports for used but not imported symbols
  • source.fixAll.ts - despite the name, fixes a couple of specific issues: unreachable code, await in non-async functions, incorrectly implemented interface
  • source.removeUnused.ts - removes declared but unused variables
  • source.organizeImports.ts - organizes and removes unused imports

Goto Source Definition command

TypeScript 4.7+ supports Go To Source Definition. It’s similar to Go To Definition, but it never returns results inside declaration files. Instead, it tries to find corresponding implementation files (like .js or .ts files), and find definitions there — even if those files are normally shadowed by .d.ts files.

This comes in handy most often when you need to peek at the implementation of a function you're importing from a library instead of its type declaration in a .d.ts file.

Run LSP-typescript: Goto Source Definition from the Command Palette to invoke this functionality or bind lsp_typescript_goto_source_definition to a custom key binding.

Find Callers command

The LSP-typescript: Find Callers command can be used to find what is calling the given symbol. It has some overlap with the built-in LSP: Find References command but returns only the places where the symbol was called.

Inlay hints

Inlay hints are short textual annotations that show parameter names, type hints.

inlay-hints

To enable inlay hints: 1. Open the command palette and select Preferences: LSP Settings, then enable show_inlay_hints: “js { "show_inlay_hints”: true }

2. Modify the following settings through `Preferences: LSP-typescript Settings`:

```js
{
  "settings": {
    // Javascript inlay hints options.
    "javascript.inlayHints.includeInlayEnumMemberValueHints": false,
    "javascript.inlayHints.includeInlayFunctionLikeReturnTypeHints": false,
    "javascript.inlayHints.includeInlayFunctionParameterTypeHints": false,
    "javascript.inlayHints.includeInlayParameterNameHints": "none",
    "javascript.inlayHints.includeInlayParameterNameHintsWhenArgumentMatchesName": false,
    "javascript.inlayHints.includeInlayPropertyDeclarationTypeHints": false,
    "javascript.inlayHints.includeInlayVariableTypeHints": false,
    // Typescript inlay hints options.
    "typescript.inlayHints.includeInlayEnumMemberValueHints": false,
    "typescript.inlayHints.includeInlayFunctionLikeReturnTypeHints": false,
    "typescript.inlayHints.includeInlayFunctionParameterTypeHints": false,
    "typescript.inlayHints.includeInlayParameterNameHints": "none",
    "typescript.inlayHints.includeInlayParameterNameHintsWhenArgumentMatchesName": false,
    "typescript.inlayHints.includeInlayPropertyDeclarationTypeHints": false,
    "typescript.inlayHints.includeInlayVariableTypeHints": false,
  }
}

Note: Inlay hints require TypeScript 4.4+.

Usage in projects that also use Flow

TypeScript can check vanilla JavaScript, but may break on JavaScript with Flow types in it. To keep LSP-typescript enabled for TS and vanilla JS, while ignoring Flow-typed files, you must install JSCustom and configure it like so:

{
  "configurations": {
    "Flow": {
      "scope": "source.js.flow",
      "flow_types": true,
      "jsx": true
    }
  }
}

Also install ApplySyntax and configure it like so:

{
  "syntaxes": [
    {
      "syntax": "User/JS Custom/Syntaxes/Flow",
      "match": "all",
      "rules": [
        { "file_path": ".*\\.jsx?$" },
        { "first_line": "^/[/\\*] *@flow" }
      ]
    }
  ]
}

And then configure LSP-typescript like so:

{
  "selector": "source.js - source.js.flow, source.jsx, source.ts, source.tsx"
}

This works only on Sublime Text 4, and your project must have a // @flow or /* @flow */ in each Flow-typed file. For more information, see this issue.