Lint Runner
Run your project's own linter on the open file and see the problems in the editor: red wavy underlines for errors, amber for warnings, a dot in the gutter, the message on hover, a count in the status bar, a list to jump through (Alt+F8 goes to the next one).
| Linter | For | Needs |
|---|---|---|
| ESLint | JavaScript, TypeScript, Vue, Svelte | ESLint in your project (npx eslint) |
| Ruff | Python | ruff on your PATH |
| Stylelint | CSS, SCSS, Less | Stylelint in your project |
How it works, honestly
The extension cannot read the terminal. It types the linter command in the terminal (you see it) with an option that makes the linter write its JSON report to .ferrum/lint/, then reads that file and paints the result. If the linter is missing or crashes, no report arrives and you are told to look at the terminal. Turn on lintRunner.onSave to check on every save.
Uses the decorations API (Ferrum 0.3.1 and later).
Permissions
terminal to run the linter, workspace.read and workspace.write for the report file.