static-code-analysis-typescript

Install eslint, @eslint/js, typescript-eslint, and globals as dev dependencies, then create an eslint.config.mjs exporting a flat config array. Add typescript-eslint recommended configs, scope TypeScript rules to .ts files, and place eslint-config-prettier last to disable conflicting formatting rules.

Uninstall the trivago plugin, install eslint-plugin-simple-import-sort, and remove all importOrder options from .prettierrc.json. Add simple-import-sort/imports and simple-import-sort/exports rules to your ESLint config, remove source.organizeImports from VS Code settings, then run npx eslint . --fix to normalize all imports.

The preferred modern baseline uses Prettier CLI for formatting validation and ESLint only for code-quality rules, with eslint-config-prettier disabling conflicts. Using eslint-plugin-prettier is acceptable when a repo intentionally splits TS and non-TS formatting and documents that split clearly.

VS Code's built-in source.organizeImports conflicts with ESLint or Prettier import sorting plugins, producing competing orderings on every save. Remove source.organizeImports from .vscode/settings.json and let eslint-plugin-simple-import-sort handle import order instead.

Prefer adding a quality job to an existing CI workflow and making the test job depend on it via needs: quality. Only create a standalone quality workflow when the repository has no existing pipeline, since integration gives one status check and avoids wasting CI minutes.

Running full-project tsc --noEmit on every commit adds significant latency. Keep lint-staged in pre-commit for fast staged-file checks, and move tsc:check to pre-push or rely on CI as the authoritative type-checking gate.