for Windows and Linux
for macOS Ctrl+Alt+S
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 and configure a new one.
In this field, specify the version of the TypeScript to use (CLion displays the currently chosen version).
By default, the
typescriptpackage from the project's node_modules folder is used.
Bundled: choose this option to use the
typescriptpackage that is shipped with CLion without attempting to find another one.
Select: choose this option to use a custom
typescriptpackage instead of the one bundled with CLion. 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
typescriptpackage installed via Yarn 2. In this case,
yarn:package.json:typescriptis 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 CLion.
|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|
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:
Alternatively, click 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