Skip to content

chore: replace eslint with oxlint - #4

Merged
Adebesin-Cell merged 2 commits into
mainfrom
chore/replace-eslint-with-oxlint
Aug 11, 2026
Merged

Adebesin-Cell merged 2 commits into
mainfrom
chore/replace-eslint-with-oxlint

Conversation

@Adebesin-Cell

@Adebesin-Cell Adebesin-Cell commented Aug 11, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #

📚 Description

Replaces ESLint with oxlint (the oxc linter) across the repo, and wires linting into CI. One fast binary instead of per-app eslint + eslint-config-next, no config file to maintain, and the whole tree lints from the root.

⛳️ Current behavior

Each Next app carried the create-next-app ESLint default — eslint + eslint-config-next in devDeps and its own eslint.config.mjs. CI never ran lint, so nothing enforced it.

🚀 New behavior

  • Root: added oxlint with lint / lint:fix scripts; pnpm lint lints the whole tree.
  • Next apps (panda-app, standalone-app, monorepo/apps/web): removed eslint / eslint-config-next and their eslint.config.mjs, repointed pnpm lint at oxlint.
  • CI: added a pnpm lint step to the quality job.
  • Regenerated the example lockfiles; refreshed the ESLint mentions in AGENTS.md and CONTRIBUTING.md.

No .oxlintrc.json — defaults are enough for now; the repo lints clean today. Add one when a rule needs tuning.

💣 Is this a breaking change?

No.

📝 Additional information

The large lockfile diffs are just ESLint's dependency tree being removed.

Swap the Next apps' eslint/eslint-config-next setup for oxlint, and add oxlint at the repo root. oxlint is the oxc linter (https://oxc.rs/docs/guide/usage/linter): one binary, no config needed, and it lints the whole tree from the root.
@Adebesin-Cell
Adebesin-Cell merged commit e27a162 into main Aug 11, 2026
1 check passed
@Adebesin-Cell
Adebesin-Cell deleted the chore/replace-eslint-with-oxlint branch August 11, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant