Skip to main content

IDE Integration (VS Code)

This guide focuses on stable, low-noise integration with the VS Code ESLint extension.

Extension expectationsโ€‹

Install and enable:

  • dbaeumer.vscode-eslint (official VS Code ESLint extension)

Recommended checks:

  • workspace is trusted,
  • project dependencies are installed,
  • VS Code uses the same Node version as your terminal/CI.

Flat Config sampleโ€‹

// eslint.config.mjs
import typefest from "eslint-plugin-typefest";

export default [
  {
    files: ["**/*.{ts,tsx}"],
    plugins: {
      typefest,
    },
    rules: {
      ...typefest.configs.recommended.rules,
    },
  },
];

Type-aware parser setup notesโ€‹

typefest.configs.recommended already enables projectService.

If you build a fully manual config block (instead of consuming a preset), configure parser services in the TypeScript-targeted config block:

languageOptions: {
  parserOptions: {
    projectService: true,
    tsconfigRootDir: import.meta.dirname,
  },
}

If parser services are missing, typed rules may not run as expected.

Common gotchasโ€‹

  • File is outside tsconfig scope: typed rules may silently skip behavior.
  • Mismatched Node versions: CLI and VS Code show different diagnostics.
  • Stale extension process: reload the VS Code window after dependency upgrades.
  • Conflicting formatters/fixers: verify on-save actions are not undoing ESLint fixes.

Validation checklistโ€‹

  • npm run typecheck
  • npm run test
  • npm run lint:all:fix:quiet

If CLI is clean but VS Code is noisy, start with --print-config and extension output logs.