RubyMine 2020.2 Help

TypeScript

File | Settings | Languages and Frameworks | TypeScript for Windows and Linux

RubyMine | Preferences | Languages and Frameworks | TypeScript for macOS Ctrl+Alt+S the Settings/Preferences icon

Node interpreter

In this field, specify the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.

TypeScript

In this field, specify the version of the TypeScript to use (RubyMine displays the currently chosen version).

  • By default, the typescript package from the project's node_modules folder is used.

  • Bundled: choose this option to use the typescript package that is shipped with RubyMine without attempting to find another one.

  • Select: choose this option to use a custom typescript package instead of the one bundled with RubyMine. In the dialog that opens, choose the path to the relevant package.

  • If your project package manager is Yarn 2, you have to use the typescript package installed via Yarn 2. In this case, yarn:package.json:typescript is by default selected.

    Learn more about package managers from npm and Yarn.

TypeScript Language Service

Select this checkbox to get native support from the TypeScript Language Service according to the up-to-date specifications. As a result:

  • Syntax and error highlighting is based on the annotations from the TypeScript Language Service.

  • Completion lists contain both suggestions from the TypeScript Language Service and suggestions calculated by RubyMine.

  • TypeScript code is compiled into JavaScript.

ItemDescription
Also for projects without tsconfig.json When this checkbox is selected, the TypeScript Language Service also processes projects that do not contain a tsconfig.json configuration files. In this case, the default scope is the entire project.
Recompile on changes
  • When this checkbox is selected, the compiler "wakes up" upon any change to a TypeScript file.

  • When this checkbox is cleared, the compiler ignores changes to TypeScript files.

Compile scope

From this list, choose the scope in which the compiler will work when you click Compile and choose Compile All in the TypeScript tool window. The available options are:

  • All Places: all the scopes listed below.

  • Project Files: all the files within the project content roots (see Project structure).

  • Project Production Files: all the files within the project content roots excluding test sources.

  • Project Test Files: all the files within the project test source roots.

  • Scratches and Consoles: all the files from the Scratches and Consoles directory located in the Project tool window.

  • Open Files: all the files that are currently opened in the editor.

  • Current File: the file opened in the active editor tab.

VCS Scopes: these scopes are only available if your project is under version control.

  • All Changed Files: all changed files, that is, all files associated with all existing changelists.

  • Default Changelist: all the files associated with the changelist  Default.

Alternatively, click the Browse button and configure a custom scope in the Scopes dialog that opens.

For more details on scopes, see the pages Scopes and Scopes dialog.
Options

In this field, specify the command-line options to be passed to the TypeScript Language Service when the tsconfig.json file is not found. See the list of acceptable options at TSC arguments. Note that the -w or --watch (Watch input files) option is irrelevant.

Last modified: 31 August 2020