Run oxlint before ESLint in web lint scripts

[lyzno1]

Summary

The web lint setup uses to disable ESLint rules already covered by oxlint, but the oxlint CLI never runs in the lint scripts. This leaves the disabled rules unchecked.

Proposal

• Add oxlint CLI as a dev dependency for .
• Add a script (e.g., ).
• Update // (and related) scripts to run oxlint before ESLint so the disabled rules are still enforced.

[lyzno1]

@dosubot validate this issue, explain the eslint-plugin-oxlint.

[dosubot]

The issue is valid: since some ESLint rules are disabled in favor of oxlint coverage, running oxlint before ESLint in your lint scripts is necessary to ensure those rules are still enforced. Without running the oxlint CLI, any rules disabled in ESLint but covered by oxlint would go unchecked.

eslint-plugin-oxlint is an ESLint plugin that automatically disables ESLint rules which are already handled by oxlint. This prevents duplicate checks and speeds up linting, especially in larger projects. The recommended workflow is to run oxlint first (to catch those rules), then run ESLint for the remaining rules—typically React-specific ones, since ESLint is officially maintained by the React team for those cases. This setup is already reflected in the Dify project, where eslint-plugin-oxlint is enabled and detects rules from your .oxlintrc.json config file. For more details, see the discussion and configuration references here and here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}