Cloudflare shares its Oxlint rules for JavaScript teams
Cloudflare has published its shared Oxlint configuration for JavaScript and TypeScript projects. Version 0.1.0 of @cloudflare/oxlint-config was published on 20 November, according to the npm…
Cloudflare has published its shared Oxlint configuration for JavaScript and TypeScript projects. Version 0.1.0 of @cloudflare/oxlint-config was published on 20 November, according to the npm registry.
For teams maintaining Shopify apps, the release offers a concrete set of linting choices to review against their own codebase. It is a developer tool, not a Shopify requirement or a merchant setting.
Rules with a migration path
The official repository describes a preset built on the @nkzw configuration, with Cloudflare's choices around correctness, types, promises and type imports. Its setup uses Oxlint with the TypeScript rules package and requires Node 22.18 or later on the 22 line, or Node 24 and later.
Cloudflare recommends spreading the preset at the root of the configuration so its environment settings survive, then placing project specific settings afterwards. Teams should follow the repository's current dependency versions instead of assuming their existing toolchain is compatible.
Keep type checking and review exceptions
Type aware linting is not a replacement for a separate compiler type check. Keep the type checking step in CI, and test how the preset handles the frameworks and callback patterns your application uses.
The repository recommends migrating from a passing commit, disabling incompatible rules initially and enabling them one at a time. That makes changes reviewable and helps distinguish a useful finding from a rule that needs a project specific exception.
Cloudflare also disables whole category defaults so an upgrade does not silently enable a new collection of rules. That is worth preserving when adapting the preset: a lint upgrade should not unexpectedly change the acceptance criteria for a production release.
There is no project specific speed benchmark in this announcement. Before replacing an existing ESLint pipeline, measure the candidate configuration on your own repository and check which existing checks still need another tool.
View the original announcement on X
More from News
See all →
