# JavaScript linters

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/go/2026.3/llms.txt).

> **TL;DR**
> Required plugin:
>
>
>
> `JavaScript and TypeScript` -    the plugin is bundled with GoLand and enabled by default.

GoLand integrates with [ESLint](http://eslint.org/) and other most popular JavaScript code linters that detect problems in your code without executing it.

When installed and enabled, a linter activates automatically every time you open a JavaScript file, reports detected errors and warnings, 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](#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/help/img/idea/2026.3/inspection-widget.png)

## Problems tool window

For each error GoLand shows a brief description and the number of the line where the error occurred. From an error message, you can navigate to the code where the problem occurred, or apply a quick-fix, or fix the problem manually in the Editor Preview pane (![the Open Preview button](https://resources.jetbrains.com/help/img/idea/2026.3/app.actions.previewDetails.svg)).

Procedure:

* To open the Problems tool window, click the Inspections widget in the upper-right corner of the editor.

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

Alternatively, select `View | Tool windows | Problems` from the main menu or press `Alt+6` (Windows), `⌘ 6` (macOS), `⌘ 6` (IntelliJ IDEA Classic (macOS)), `⌘ 6` (macOS System Shortcuts), `Alt+6` (XWin), `Alt+6` (GNOME), `Alt+6` (KDE), `Alt+6` (Emacs), `Alt+6` (Sublime Text), `⌘ 6` (Sublime Text (macOS)), `Ctrl+Shift+M` (VSCode), `⌘ ⇧ M` (VSCode (macOS)).

* In the File tab, view the errors detected in the file from the active editor tab.

![Quick-fixes in the Problems tool window](https://resources.jetbrains.com/help/img/idea/2026.3/ws_js_eslint_problems_tw.png)

* In the Project Errors tab, view the errors in all previously opened files, with error messages grouped by files in which they were detected.

![Problems tool window, ESLint. Project Errors tab shows syntax errors in previously opened files across the project](https://resources.jetbrains.com/help/img/idea/2026.3/ws_problems_toolwindow_project_errors_linters.png)

*

* To view suggested quick-fixes for a problem, select the corresponding error message and then select Show Quick Fixes from its context menu, or click ![the Show Quick Fixes button](https://resources.jetbrains.com/help/img/idea/2026.3/app.expui.codeInsight.intentionBulb.png) on the toolbar, or just press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `Ctrl+.` (VSCode), `⌘ .` (VSCode (macOS)).

To fix a problem, select the appropriate quick-fix from the list.

* Alternatively, click ![the Open Editor Preview button](https://resources.jetbrains.com/help/img/idea/2026.3/app.actions.previewDetails.svg) to open the Editor Preview pane and fix the problem manually there, without leaving the tool window.

* To resolve the detected problems in the whole file, select <Linter name >: Fix current file from the context menu.

* To navigate to the place where an error occurred, double-click the corresponding error message, or select Jump to Source from its context menu, or just press `F4` (Windows), `⌘ ↓` (macOS), `F4` (IntelliJ IDEA Classic (macOS)), `F4` (macOS System Shortcuts), `F4` (XWin), `F4` (GNOME), `F4` (KDE), `F4` (Emacs), `F4` (Sublime Text), `F4` (Sublime Text (macOS)), `F4` (VSCode), `F4` (VSCode (macOS)).

* You can also edit the linter's settings, suppress a rule in the statement where a problem occurred or in the whole file, as well as exclude the current file from analysis. See [Disable and suppress inspections](disabling-and-enabling-inspections.html) for details.

* To filter out error messages by their severity and customize their sorting, click ![the View Options button](https://resources.jetbrains.com/help/img/idea/2026.3/app.general.inspectionsEye.svg) and select or clear the relevant items in the list.

* To copy an error message, select Copy Problem Description from its context menu or press `Ctrl+C` (Windows), `⌘ C` (macOS), `⌘ C` (IntelliJ IDEA Classic (macOS)), `⌘ C` (macOS System Shortcuts), `Ctrl+C` (XWin), `Ctrl+C` (GNOME), `Ctrl+C` (KDE), `Ctrl+C` (Emacs), `Ctrl+C` (Sublime Text), `⌘ C` (Sublime Text (macOS)), `Ctrl+C` (VSCode), `⌘ C` (VSCode (macOS)).

