# JSCS

> **TL;DR**
> Required plugin:
>
>
>
> `JavaScript and TypeScript` -    the plugin is bundled with CLion and enabled by default.
>
>
>
> `[JSCS](https://plugins.jetbrains.com/plugin/14446-jscs)` -    install the plugin on the Settings | Plugins page, tab Marketplace.

> **Warning:**
> Since CLion 2020.2, JSCS support in the IDE has been deprecated, refer to the [JSCS official website](https://jscs-dev.github.io/) for details.
>
>
>
> However, JSCS support is still available through the JSCS plugin, which can be installed on the Settings | Plugins page as described in [Installing plugins from JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo).

When [JSCS support is enabled](#ws_js_linters_jscs_enable_and_configure), CLion highlights errors that [JSCS](https://eslint.org/blog/2016/04/welcoming-jscs-to-eslint) detects, provides descriptions for them, and suggests quick-fixes where possible.

Descriptions of the errors detected in the current file and quick-fixes for them are available from the editor and from the File tab of the [Problems](linters.html#ws_js_linters_general_problems_tool_window) tool window.

Errors in all previously opened files and quick-fixes for them are shown in the Project Errors tab of the Problems tool window. To open the tool window, click the Inspection widget in the upper-right corner of the editor:

![Inspection widget](https://resources.jetbrains.com.cn/help/img/idea/2026.2/inspection-widget.png)

For more information, refer to [View problems and
apply quick-fixes in the editor](linters.html#ws_js_linters_editor) and [Problems tool window](linters.html#ws_js_linters_general_problems_tool_window).

CLion also provides code completion in JSCS configuration files.

Procedure: Before you start

1. Download and install [Node.js](http://nodejs.org/#download).

2. Install and enable the JSCS plugin on the Settings | Plugins page, tab Marketplace, as described in [Installing plugins from
JetBrains Marketplace](managing-plugins.html#install_plugin_from_repo).

If the JSCS repository plugin is missing, CLion suggests installing it when you open a `.jscsrc` or a `.jscs.json` configuration file.

![CLion suggests installing JSCS plugin](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_jscs_install_plugin_from_config.png)

Procedure: Install JSCS globally

* In your command-line shell or in the embedded Terminal (`Alt+F12` (Windows), `⌥ F12` (macOS), `⌥ F12` (IntelliJ IDEA Classic (macOS)), `⌘ ⌃ T` (macOS System Shortcuts), `Alt+F12` (XWin), `Alt+F12` (GNOME), `Alt+F12` (KDE), `Alt+F12` (Emacs), `Alt+F12` (Sublime Text), `⌥ F12` (Sublime Text (macOS)), `⌥ F12` (Xcode), `Ctrl+Alt+1` (Visual Studio), `⌘ ⌃ 1` (Visual Studio (macOS)), `Ctrl+Alt+1` (ReSharper), `⌘ ⌃ 1` (ReSharper (macOS)), `Alt+F12` (QtCreator), `⌥ F12` (QtCreator (macOS)), `Alt+F12` (NetBeans), `Alt+F12` (Eclipse), `⌥ F12` (Eclipse (macOS))) , type:

`npm install --g jscs`

Procedure: Enable JSCS and configure its behavior in CLion

1. In the Settings dialog (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS))), go to  `Languages & Frameworks | JavaScript | Code Quality Tools | JSCS`. On the JSCS page, that opens, select the Enable checkbox. After that the other controls on the page become available.

2. In the Node runtime field, specify the path to Node.js.  If you followed the standard installation procedure, CLion detects the path and fills in the field itself.

3. In the JSCS Package field, specify the location of the `jscs` package.

If you installed JSCS through the Node Package Manager, CLion locates the package itself and fills in the field automatically. Otherwise, type the path manually or click ![](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.openDiskHover.svg) and select the package location in the dialog that opens.

4. Specify the configuration to use.

* Search for config(s) - select this option if JSCS rules are configured in your project `package.json`, in `.jscsrc`, or in `.jscs .json`. CLion will first look for a `jscsConfig` property in the project `package .json`. If no `jscsConfig` property is found, CLion will look for a `.jscsrc` or a `.jscs.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 the project root is reached.

* Configuration File - select this option if JSCS rules are configured in a custom JSON file. Specify the file location in the Path field. Select the path from the list or click ![the Browse button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.general.ellipsis.svg) and select the relevant file in the dialog that opens.

5. To apply a predefined set of rules associated with the code style you are using, select the set from the Code Style Preset list.

> **Tip:**
> You can use the selected set independently or in addition to a configuration file. Note that rules from configuration files override predefined rules.

## See also

### Procedures