You can use the TSLint code verification tool from inside CLion and check your TypeScript code for most common mistakes without running the application. When the tool is activated, it lints all the opened TypeScript files and marks the detected problems.
To view the description of a problem, hover over the highlighted code.
By default, CLion marks detected problems based on the severity levels from the TSLint configuration file. See Configuring TSLint highlighting to learn how to override these settings.
Before you start
In the embedded Terminal (Alt+F12) , type:
npm install tslint typescript --save-dev
Learn more from the TSLint official website.
Activating and configuring TSLint in CLion
By default, CLion uses the TSLint package from the project node_modules folder and the tslint.json configuration file from the folder where the current file is stored. If no tslint.json is found in the current file folder, CLion will look for one in its parent folders up to the project root.
If you have several package.json files with TSLint listed as a dependency, CLion starts a separate process for each package.json and processes everything below it. This lets you apply a specific TSLint version or a specific set of plugins to each path in a monorepo or a project with multiple TSLint configurations.
This behavior is default in all new CLion projects. To enable it in a previously created project, go to Settings/Preferences dialog Ctrl+Alt+S and select the Automatic TSLint configuration option.in the
You can also configure TSLint manually to use a custom TSLint package and tslint.json and specify some additional rules.
In the Settings/Preferences dialog Ctrl+Alt+S, go to .
Select the Manual Configuration option.
Specify the Node.js interpreter to use and the path to the TSLint package.
In the Configuration File area, appoint the configuration to use.
By default, CLion first looks for a tslint.json, tslint.yaml, or tslint.yml 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, tslint.yaml, or tslint.yml configuration file is found, TSLint uses its default embedded configuration file. Accordingly, you have to define the configuration to apply either in a tslint.json, tslint.yaml, or tslint.yml configuration file, or in a custom configuration file, or rely on the default embedded configuration.
To have CLion look for a tslint.json, tslint.yaml, or tslint.yml file, choose the Automatic search option.
To use a custom file, choose the Configuration File option and specify the location of the file in the Path field. Choose the path from the list, or type it manually, or click and select the relevant file from the dialog that opens.
Learn more about configuring TSLint from the TSLint official website.
If necessary, in the Additional Rules Directory field, specify the location of the files with additional code verification rules. These rules will be applied after the rules from tslint.json, tslint.yaml, tslint.yml, or from the above specified custom configuration file and accordingly will override them.
Configuring highlighting for TSLint
By default, CLion marks the detected errors and warnings based on the severity levels from the TSLint configuration file. For example, errors are highlighted with a red squiggly line, while warnings are marked with a yellow background. See Static code analysis and Inspection severities for details.
Change the severity level of a rule in the TSLint configuration
In TSLint configuration file, locate the rule you want to edit and set its ID to
error. Learn more from the TSLint official website.
You can override the severities from the TSLint configuration file so that CLion ignores them and shows everything reported by the linter as errors, warnings, or in a custom color.
Ignore the severity levels from the configuration
In the Settings/Preferences dialog Ctrl+Alt+S, go to . The Inspections page opens.
In the central pane, go to TypeScript | TSLint.
In the right-hand pane, clear the Use rule severity from the configuration file checkbox and select the severity level to use instead of the default one.
Importing code style from a TSLint configuration file
CLion understands some of the TSLint rules described in tslint.json, tslint.yaml, or tslint.yml configuration files and lets you apply them to the TypeScript code style configuration in your project.
When you open your project for the first time, CLion imports the code style from the project tslint.json, tslint.yaml, or tslint.yml automatically.
If tslint.json, tslint.yaml, or tslint.yml is updated (manually or from your version control), open it in the editor and choose Apply TSLint Code Style Rules from the context menu.
Alternatively, just answer Yes to the "Apply code style from TSLint?" question on top of the file.
CLion lets you automatically fix some of the issues reported by TSLint.
To fix a specific error, place the cursor at the highlighted code, press Alt+Enter, and then select TSLint: fix current error from the list.
To fix all the issues detected in the file, choose TSLint: fix current file.
You can suppress TSLint rules for the current file and even for the current line. CLion automatically generates disable comments in the format
/* tslint:disable:<rule name> or
// tslint:disable-next-line:<rule name> and places them on top of the file or above the current line respectively.
Suppress a TSLint rule on the fly
Place the cursor at an error or a warning reported by TSLint and press Alt+Enter.
Select the quick-fix for the rule that you want to disable and press Right.
From the list, select Suppress <rule name> for current file or Suppress <rule name> for current line.