CLion 2019.1 Help


File | Settings | Languages and Frameworks | TypeScript for Windows and Linux
CLion | 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. If you choose the Project alias, CLion will automatically use the project default interpreter from the Node interpreter field on the Node.js and NPM page.

In most cases, CLion detects the project default interpreter and fills in the field itself. You can also choose another configured local interpreter or click the Browse button and configure a new one.


From this list, choose the version of the TypeScript to use (CLion 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 comes bundled with CLion without attempting to find another one.

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

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 CLion.

  • TypeScript code is compiled into JavaScript.



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. To re-activate the compiler, open the TypeScript Tool Window (View | Tool Windows | TypeScript), click icon_ts_compile_all on the toolbar, and choose the compilation scope from the list:

    If you have not opened the TypeScript tool window yet and it is not available from the View menu, choose Help | Find Action, then find and launch the TypeScript Compile All action from the list.

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 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.

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

For more details on scopes, see Scopes dialog.


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: 24 July 2019