@rikalabs/oxlint-standards

Strict, opinionated Oxlint defaults for TypeScript projects, with a full anti-slop baseline. Drizzle, Next App Router, and Effect guardrails are opt-in presets (strict-full or individual packs).

This package ships two things:

• shared Oxlint presets (presets/*.json)
• a custom JS plugin (@rikalabs/*) for rules Oxlint does not provide natively

Goals

• enforce consistent standards across repositories
• prefer Oxlint built-ins first, custom rules second
• keep custom rules architecture-agnostic for open source reuse

Baseline policy

core-clean enables every Oxlint builtin category at error: correctness, suspicious, pedantic, perf, style, restriction, and nursery.

The package keeps explicit rule entries where we need non-default options or where the platform baseline depends on plugin-specific rules that category toggles do not cover cleanly. This keeps the default strict presets close to the production platform config while still making the intentional exceptions readable in preset JSON.

Install

bun add -d @rikalabs/oxlint-standards oxlint oxlint-tsgolint

strict depends on type-aware typescript/* rules, so consuming projects must enable root-level options.typeAware.

Migrating from ESLint

Use @oxlint/migrate to translate an existing ESLint configuration. Then add extends pointing at this package’s presets and declare jsPlugins in the root .oxlintrc.json as shown below.

Use in .oxlintrc.json

{
	"$schema": "./node_modules/oxlint/configuration_schema.json",
	"options": {
		"typeAware": true
	},
	"extends": ["./node_modules/@rikalabs/oxlint-standards/presets/strict.json"],
	"jsPlugins": ["@rikalabs/oxlint-standards/plugin"]
}

jsPlugins must be declared by the consuming project because Oxlint currently only merges rules, plugins, and overrides through extends, and options.typeAware must live in the root config.

Preset strategy

• strict and recommended are the default: TypeScript-only strictness (strict-core + strict-runtime + strict-tests, same as strict-ts). No React, Drizzle, or Effect rules unless you add them.
• strict-full composes strict-ts with strict-drizzle, strict-web (Next App Router and React), effect-service-hygiene, and effect-observability. Use it when you want the full Rika stack in one extend.
• strict-next is a thin alias of strict-web. Compose strict + strict-next for Next-only frontends.
• strict-effect extends strict-full (same rules as strict-full in one preset name).
• effect-observability is observability-only: it currently enforces span naming without bringing in the broader Effect runtime/service doctrine.
• For the broader Effect stack, add effect-service-hygiene (which pulls in the runtime/composition/error-model chain) alongside effect-observability, or use strict-full / strict-effect.
• anti-slop-aggressive is an opt-in extension for the more taste-heavy helper/fallback heuristics that stay out of the default anti-slop baseline.
• Opt in individually: add strict-drizzle, strict-web, effect-observability, or anti-slop-aggressive after strict when only part of the stack applies.

Tests: Vitest, Bun, and Jest

• strict-tests is Vitest-first: it enables vitest/* rules, jsdoc checks, and @rikalabs/no-placeholder-tests / @rikalabs/no-mock-only-tests. It does not load the Jest plugin by default.
• bun:test (Bun’s built-in runner) uses import { … } from "bun:test". Oxlint’s Vitest rules apply where the linter matches test patterns; behavior can differ from running Vitest’s own CLI—treat mismatches as documentation or config gaps.
• strict-tests-jest extends strict-tests and adds Jest plugin rules for codebases that still use Jest.

Example (Next frontend only):

{
	"$schema": "./node_modules/oxlint/configuration_schema.json",
	"options": {
		"typeAware": true
	},
	"extends": [
		"./node_modules/@rikalabs/oxlint-standards/presets/strict.json",
		"./node_modules/@rikalabs/oxlint-standards/presets/strict-next.json"
	],
	"jsPlugins": ["@rikalabs/oxlint-standards/plugin"]
}

Example (opt into Drizzle + Effect observability, no Next):

{
	"$schema": "./node_modules/oxlint/configuration_schema.json",
	"options": {
		"typeAware": true
	},
	"extends": [
		"./node_modules/@rikalabs/oxlint-standards/presets/strict.json",
		"./node_modules/@rikalabs/oxlint-standards/presets/strict-drizzle.json",
		"./node_modules/@rikalabs/oxlint-standards/presets/effect-observability.json"
	],
	"jsPlugins": ["@rikalabs/oxlint-standards/plugin"]
}

Example (full stack in one preset):

{
	"$schema": "./node_modules/oxlint/configuration_schema.json",
	"options": {
		"typeAware": true
	},
	"extends": ["./node_modules/@rikalabs/oxlint-standards/presets/strict-full.json"],
	"jsPlugins": ["@rikalabs/oxlint-standards/plugin"]
}

You can also extend strict-drizzle or strict-web alone on top of strict if you are incrementally adopting rules.

Example (opt into the full Effect stack without strict-full):

{
	"$schema": "./node_modules/oxlint/configuration_schema.json",
	"options": {
		"typeAware": true
	},
	"extends": [
		"./node_modules/@rikalabs/oxlint-standards/presets/strict.json",
		"./node_modules/@rikalabs/oxlint-standards/presets/effect-service-hygiene.json",
		"./node_modules/@rikalabs/oxlint-standards/presets/effect-observability.json"
	],
	"jsPlugins": ["@rikalabs/oxlint-standards/plugin"]
}

Less verbose explicit returns

• typescript-hard-mode enables both typescript/explicit-function-return-type and typescript/explicit-module-boundary-types. If boundary types are enough, use strict-ts-boundaries (same as strict-ts but typescript/explicit-function-return-type is off) or compose from typescript-hard-mode-boundaries-only when building a custom preset chain.

Default threshold policy (in strict-core)

strict-core keeps the broader threshold family mostly off, but it does enforce a few repository-shaping caps by default:

| Rule | Default | | --- | --- | | eslint/max-lines-per-function | 60 (skipBlankLines, skipComments) | | eslint/max-classes-per-file | 1 | | eslint/max-lines | 1500 (skipBlankLines, skipComments) |

strict-core also keeps a small style-noise off-list for the default baseline: eslint/no-ternary, eslint/no-continue, eslint/no-negated-condition, eslint/id-length, eslint/max-statements, eslint/new-cap, eslint/prefer-object-spread, unicorn/no-useless-undefined, oxc/no-optional-chaining, oxc/no-rest-spread-properties, and oxc/no-map-spread.

At the strict / strict-ts layer, the default TypeScript-oriented baseline also turns off typescript/explicit-function-return-type, typescript/explicit-module-boundary-types, and eslint/no-void.

Presets

1. core-clean
2. typescript-hard-mode
3. typescript-hard-mode-boundaries-only (like typescript-hard-mode but typescript/explicit-function-return-type off)
4. imports-hygiene
5. promise-safety
6. naming-discipline
7. anti-slop-aggressive (opt-in helper/fallback heuristics trimmed from the default anti-slop baseline)
8. effect-runtime
9. effect-error-model
10. effect-composition
11. effect-service-hygiene
12. effect-observability
13. strict-core
14. strict-runtime
15. strict-drizzle
16. strict-web
17. strict-next (alias of strict-web)
18. strict-tests (Vitest + jsdoc + custom test rules; no Jest plugin)
19. strict-tests-jest (extends strict-tests with Jest plugin rules)
20. strict-ts (same layers as strict: strict-core + strict-runtime + strict-tests)
21. strict-ts-boundaries (like strict-ts but typescript/explicit-function-return-type off)
22. strict (default TypeScript-only baseline; alias chain: strict-ts)
23. strict-full (strict-ts + strict-drizzle + strict-web + strict-zustand + strict-electrobun + strict-bun + effect-service-hygiene + effect-observability)
24. strict-effect (compatibility alias: extends strict-full)
25. strict-zustand (Zustand state management guardrails)
26. strict-electrobun (Electrobun desktop app boundary rules)
27. strict-bun (Bun runtime-specific rules for shared package safety)

Also available: recommended (alias of strict), recommended-ts (alias of strict).

Custom rules

Default strict custom rules include:

• @rikalabs/no-vague-verbs
• @rikalabs/no-duplicate-context
• @rikalabs/no-import-then-reexport
• @rikalabs/no-is-record-helpers
• @rikalabs/no-trivial-runtime-guard-helpers
• @rikalabs/no-trivial-property-helpers
• @rikalabs/no-bare-wrapper-functions
• @rikalabs/no-silent-catch-fallback
• @rikalabs/no-runtime-compat-fallbacks
• @rikalabs/no-catch-return-error-object
• @rikalabs/no-unlisted-external-imports
• @rikalabs/no-double-type-assertion
• @rikalabs/no-redundant-const-assertion
• @rikalabs/no-ai-debt-comments
• @rikalabs/no-tutorial-comments
• @rikalabs/no-commented-out-code
• @rikalabs/no-debug-residue-filenames
• @rikalabs/no-json-parse-default-fallback
• @rikalabs/no-json-stringify-default-fallback
• @rikalabs/no-as-never
• @rikalabs/drizzle-enforce-delete-with-where
• @rikalabs/drizzle-enforce-update-with-where
• @rikalabs/drizzle-no-unbounded-select
• @rikalabs/drizzle-no-raw-sql-crud
• @rikalabs/drizzle-require-transaction-scope
• @rikalabs/drizzle-require-infer-types
• @rikalabs/drizzle-require-references-callback
• @rikalabs/drizzle-no-driver-query-in-domain
• @rikalabs/drizzle-no-query-in-loops
• @rikalabs/next-no-browser-api-in-server-component
• @rikalabs/next-require-server-directive-in-actions
• @rikalabs/next-no-use-client-in-root-files
• @rikalabs/next-no-pages-router-api-in-app-dir
• @rikalabs/effect-no-raw-promises
• @rikalabs/effect-no-try-catch
• @rikalabs/effect-no-async-await
• @rikalabs/effect-no-looped-effects
• @rikalabs/no-placeholder-implementation
• @rikalabs/no-low-signal-public-names
• @rikalabs/no-low-signal-variable-names
• @rikalabs/no-generic-module-names
• @rikalabs/no-identical-branches
• @rikalabs/no-copy-paste-exports
• @rikalabs/no-standalone-classes
• @rikalabs/no-hardcoded-secrets
• @rikalabs/no-sql-string-concat
• @rikalabs/no-anemic-errors

anti-slop-aggressive additionally adds:

• @rikalabs/no-single-use-trivial-helpers
• @rikalabs/no-property-default-fallbacks

The default anti-slop baseline still includes:

• @rikalabs/no-pass-through-intermediate-vars

strict-tests also adds:

• @rikalabs/no-placeholder-tests
• @rikalabs/no-mock-only-tests

Effect rules included when you extend strict-full or effect-service-hygiene also include:

• @rikalabs/effect-no-or-die
• @rikalabs/effect-catch-handler-must-use-error
• @rikalabs/effect-no-terminal-runners
• @rikalabs/effect-no-generic-error-fail
• @rikalabs/effect-prefer-gen-over-flatmap-chain
• @rikalabs/effect-no-effect-return-in-map
• @rikalabs/effect-require-span-name
• @rikalabs/effect-no-mutable-ref-in-gen

effect-observability alone adds:

• @rikalabs/effect-require-span-name

strict-web also adds:

• @rikalabs/react-no-inline-effect-run

strict-zustand adds:

• @rikalabs/zustand-no-store-outside-store-dir
• @rikalabs/zustand-no-direct-set-in-components

strict-electrobun adds:

• @rikalabs/electrobun-no-rpc-in-domain
• @rikalabs/electrobun-no-process-global-in-renderer

strict-bun adds:

• @rikalabs/bun-no-bun-specific-in-shared

Coverage map

| Complaint family | Coverage | | --- | --- | | Defensive helper/type guard slop | @rikalabs/no-is-record-helpers, @rikalabs/no-trivial-runtime-guard-helpers, @rikalabs/no-trivial-property-helpers | | Helper hell / indirection / intermediate vars | @rikalabs/no-bare-wrapper-functions, @rikalabs/no-copy-paste-exports, @rikalabs/no-identical-branches | | Fail-fast over fallback defaults | @rikalabs/no-silent-catch-fallback, @rikalabs/no-runtime-compat-fallbacks, @rikalabs/no-json-parse-default-fallback, @rikalabs/no-json-stringify-default-fallback | | Aggressive helper/fallback heuristics | anti-slop-aggressive: @rikalabs/no-single-use-trivial-helpers, @rikalabs/no-pass-through-intermediate-vars, @rikalabs/no-property-default-fallbacks | | Comments / debug residue / AI narration | @rikalabs/no-ai-debt-comments, @rikalabs/no-tutorial-comments, @rikalabs/no-commented-out-code, @rikalabs/no-debug-residue-filenames, eslint/no-warning-comments, eslint/no-debugger, eslint/no-console | | TypeScript escape hatches | typescript/no-explicit-any, typescript/no-non-null-assertion, typescript/no-unnecessary-type-assertion, @rikalabs/no-double-type-assertion, @rikalabs/no-as-never, @rikalabs/no-redundant-const-assertion, typescript/consistent-type-definitions | | Naming / readability / structure | @rikalabs/no-vague-verbs, @rikalabs/no-low-signal-public-names, @rikalabs/no-low-signal-variable-names, @rikalabs/no-generic-module-names, @rikalabs/no-standalone-classes, eslint/max-params, eslint/max-depth, eslint/max-lines-per-function, eslint/complexity, eslint/no-nested-ternary | | Tests with placeholders or only mocks | vitest/* (default), optional Jest rules via strict-tests-jest, @rikalabs/no-placeholder-tests, @rikalabs/no-mock-only-tests | | Security / secrets / SQL string building | @rikalabs/no-hardcoded-secrets, @rikalabs/no-sql-string-concat | | Electrobun boundary safety | @rikalabs/electrobun-no-rpc-in-domain, @rikalabs/electrobun-no-process-global-in-renderer | | Zustand state management | @rikalabs/zustand-no-store-outside-store-dir, @rikalabs/zustand-no-direct-set-in-components | | Bun runtime boundaries | @rikalabs/bun-no-bun-specific-in-shared | | React + Effect integration | @rikalabs/react-no-inline-effect-run | | Effect mutable state in generators | @rikalabs/effect-no-mutable-ref-in-gen |

Explicit non-goals in the TypeScript-only default (strict) v1:

• no project-specific banned API inventories
• no deprecated-API catalog
• no heuristic React error-boundary rule
• no generic “missing validation” rule detached from concrete AST patterns

Built-in overlap policy

Custom rules must not duplicate Oxlint built-ins.

• Rule catalog: src/plugin/rule-catalog.json
• Verification script: scripts/check-builtin-overlap.ts

Run:

bun run check:builtins

Development

bun install
bun run check

Publishing is automated: create a GitHub release from a version tag (for example v0.5.0). The Publish workflow runs tests and publishes @rikalabs/oxlint-standards to npm when the release is published.

See CONTRIBUTING.md for how to change rules and presets. The minimal consumer example mirrors npm-style extends (config in oxlint.smoke.json so it does not conflict with a parent .oxlintrc.json) and is exercised in CI.

Additional shadow smoke repos exercise preset composition with both passing source files and failing fixtures:

• examples/smoke-strict-full/
• examples/smoke-strict-web/
• examples/smoke-strict-drizzle/
• examples/smoke-effect/
• examples/smoke-strict-tests/

Each smoke repo runs bun run lint against src/ and bun run lint:fixtures against fixtures/, asserting that the preset under test still reports the expected minimum number of failures.