linting-neostandard-eslint9

Install both packages with npm install --save-dev eslint@9 neostandard, then create eslint.config.js that imports neostandard and exports neostandard(). Verify the setup by running npx eslint . and add a lint script to package.json.

Install neostandard and eslint, then run npx neostandard --migrate to generate eslint.config.js from your existing package.json standard settings. Replace lint scripts with eslint ., uninstall standard, and remove obsolete standard-specific editor integrations.

Yes, neostandard supports TypeScript by setting ts: true in the config options, which lints .ts and .d.ts files. For module and import correctness in TypeScript-heavy projects, pairing it with tsc --noEmit is recommended.

neostandard is a shared ESLint flat config built for ESLint v9, while standard is a standalone linter using legacy config and standard-engine. With neostandard you run linting through eslint directly, and as of v1 it no longer bundles eslint-plugin-import-x.

Common causes include mixing legacy .eslintrc files with flat config, forgetting to disable base rules when TypeScript variants are enabled, or assuming plugin presets are flat-config compatible. Migrate incrementally and compare lint issue counts before and after.

No, CI should run lint as a non-fix quality gate using npm run lint. Reserve eslint --fix for local development workflows and pre-commit hooks via lint-staged, keeping CI results deterministic.