TSLint
for Windows and Linux
for macOS
Ctrl+Alt+S 
Use this page to activate integration with the TSLint code verifier and configure its behaviour.
| Item | Description |
|---|---|
| Enable | Select this checkbox to activate TSLint in the current project. After that the other controls in the page are enabled. |
| 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 |
| TSLint Package | In this field, specify the location of the tslint package installed globally or in the current project. |
| Configuration File | In this area, appoint the configuration to use. By default, CLion first looks for a tslint.json configuration file. CLion starts the search from the folder where the file to be checked is stored, then searches in the parent folder, and so on until reaches the project root. If no tslint.json file is found, TSLint uses its default embedded configuration file. Accordingly, you have to define the configuration to apply either in a tslint.json configuration file, or in a custom JSON configuration file, or rely on the default embedded configuration.
|
| Additional Rules Directory | In this field, specify the location of the files with additional code verification rules. These rules will be applied after the rules from tslint.json or the above specified custom configuration file and accordingly will override them. |
and configure a new one. Last modified: 24 July 2018