Skip to main content
Keep extension code quality predictable before issues reach runtime. ESLint runs outside the build pipeline. Run it from your scripts or continuous integration (CI).

When ESLint is a good fit

  • You want consistent code standards across team contributions.
  • You need CI checks that catch common JS/TS mistakes early.
  • You are enforcing extension-specific quality rules before release.

ESLint capabilities

Template examples

ESLint configuration template

Preconfigured lint setup you can use immediately. new-config-eslint screenshot
Repository: examples/new-config-eslint

Usage with an existing extension

Install the core packages:
Create eslint.config.mjs:
Run lint commands from your scripts:
If no script exists yet, run:

Best practices

  • Keep lint rules in source control and apply them in CI.
  • Use lint-staged or pre-commit hooks for faster local feedback.
  • Add framework-specific plugins (for example, React) only when needed.

Next steps

  • Integrate Prettier to avoid formatting-rule conflicts.
  • Add Stylelint for stylesheet linting.