@st1ggy/linter-config 8.0.0 → 10.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (52) hide show
  1. package/README.md +94 -34
  2. package/data/linter-config-inventory.json +451 -216
  3. package/data/oxlint-config-inventory.json +1075 -1074
  4. package/data/oxlint-rule-map.json +5329 -2075
  5. package/data/oxlint-source-inventory.json +8175 -5661
  6. package/docs/OXLINT_RULE_MAPPING.md +213 -105
  7. package/docs/RULE_MAPPING.md +2 -2
  8. package/package.json +110 -19
  9. package/scripts/README.md +9 -6
  10. package/scripts/init-angular-ox.sh +4 -0
  11. package/scripts/init-nuxt-ox.sh +4 -0
  12. package/scripts/init-vue-ox.sh +4 -0
  13. package/scripts/linter-init-core.mjs +32 -15
  14. package/scripts/linter-init.mjs +4 -2
  15. package/src/eslint/configs/config.common.js +4 -1
  16. package/src/eslint/configs/config.import.js +1 -1
  17. package/src/eslint/configs/config.prettier.js +1 -1
  18. package/src/eslint/configs/config.react.js +19 -26
  19. package/src/eslint/configs/config.solid.js +1 -1
  20. package/src/eslint/configs/config.sonarjs.js +1 -1
  21. package/src/eslint/configs/config.typescript.js +6 -0
  22. package/src/eslint/configs/config.unicorn.js +8 -19
  23. package/src/eslint/configs/import-plugin.js +48 -0
  24. package/src/eslint/configs/svelte-stack.js +5 -12
  25. package/src/eslint/eslint.config.angular-ox.js +26 -0
  26. package/src/eslint/eslint.config.astro-ox.js +3 -0
  27. package/src/eslint/eslint.config.nuxt-ox.js +4 -0
  28. package/src/eslint/eslint.config.svelte-ox.js +4 -0
  29. package/src/eslint/eslint.config.vue-ox.js +17 -0
  30. package/src/eslint/ox-supplement.d.ts +39 -0
  31. package/src/oxfmt/index.d.ts +24 -0
  32. package/src/oxfmt/oxfmt.config.angular.js +3 -0
  33. package/src/oxfmt/oxfmt.config.astro.js +3 -0
  34. package/src/oxfmt/oxfmt.config.common.js +9 -1
  35. package/src/oxfmt/oxfmt.config.svelte.js +3 -0
  36. package/src/oxlint/configs/config.astro.js +134 -176
  37. package/src/oxlint/configs/config.common.js +107 -151
  38. package/src/oxlint/configs/config.next.js +365 -300
  39. package/src/oxlint/configs/config.react.js +365 -300
  40. package/src/oxlint/configs/config.solid.js +157 -223
  41. package/src/oxlint/configs/config.svelte.js +121 -190
  42. package/src/oxlint/create-config.js +1 -1
  43. package/src/oxlint/framework-rules.js +79 -0
  44. package/src/oxlint/index.d.ts +24 -0
  45. package/src/oxlint/oxlint.config.angular.js +14 -0
  46. package/src/oxlint/oxlint.config.nuxt.js +24 -0
  47. package/src/oxlint/oxlint.config.vue.js +8 -0
  48. package/src/oxlint/plugins/angular.js +1 -0
  49. package/src/oxlint/plugins/import-x.js +1 -1
  50. package/src/oxlint/plugins/nuxt.js +1 -0
  51. package/src/oxlint/plugins/react.js +1 -1
  52. package/src/oxlint/stacks.js +22 -8
package/README.md CHANGED
@@ -12,7 +12,7 @@ Oxlint/Oxfmt engines and framework-specific plugins are optional peers. The wiza
12
12
 
13
13
  ### Generate local wrapper configs
14
14
 
15
- The published CLI is invoked as **`@st1ggy/linter-config`** (see [`package.json`](package.json) `bin`). Each run writes a linter config, a formatter config and **`stylelint.config.js`** as re-exports for the selected stack. ESLint stacks use **`eslint.config.js`** and **`prettier.config.js`**. Common/React/Solid/Next Oxlint stacks use **`oxlint.config.ts`** and **`oxfmt.config.ts`**; Svelte/Astro Oxlint stacks use **`oxlint.config.ts`** and **`prettier.config.js`**.
15
+ The published CLI is invoked as **`@st1ggy/linter-config`** (see [`package.json`](package.json) `bin`). ESLint stacks write **`eslint.config.js`**, **`prettier.config.js`** and **`stylelint.config.js`**. All nine Ox stacks write only **`oxlint.config.ts`**, **`oxfmt.config.ts`** and **`stylelint.config.js`**. They never generate or require an ESLint companion. Framework templates are not linted by Oxlint.
16
16
 
17
17
  Unless **`--skip-install`** is passed: if **`package.json`** exists in the target directory, the CLI runs the detected package manager (**npm** / **pnpm** / **yarn** / **bun** from the nearest lockfile) to install **`@st1ggy/linter-config`** and only the selected stack's integration plugins. When all selected packages are already declared but missing from `node_modules`, it runs a regular install instead.
18
18
 
@@ -22,6 +22,8 @@ Pick **at most one** stack flag (default **`--common`** if omitted):
22
22
 
23
23
  **`--common-ox` · `--react-ox` · `--solid-ox` · `--next-ox` · `--svelte-ox` · `--astro-ox`**
24
24
 
25
+ **`--angular-ox` · `--vue-ox` · `--nuxt-ox`**
26
+
25
27
  **After** `npm i -D @st1ggy/linter-config`:
26
28
 
27
29
  ```bash
@@ -49,7 +51,7 @@ The CLI is interactive in a terminal. Command and stack flags preselect their va
49
51
  Older **`--eslint`** on the command line is still accepted for compatibility; **`--eslint`** is optional.
50
52
 
51
53
  - **`init` / `create`** — create only missing files (skip existing).
52
- - **`migrate` / `reinit`** — optionally remove selected legacy configs, then overwrite the selected stack's three wrapper configs.
54
+ - **`migrate` / `reinit`** — optionally remove selected legacy configs, then overwrite the selected stack's three or four wrapper configs.
53
55
 
54
56
  **Legacy filenames** (`.eslintrc.*`, `.oxlintrc.*`, `.oxfmtrc.*`, `prettier.config.cjs`, extra copies, …) are presented one by one by `migrate`; no file is deleted without confirmation. Changing engines offers the other linter and formatter configs for removal during migration. [`scripts/remove-current.sh`](scripts/remove-current.sh) remains available as a standalone cleanup helper.
55
57
 
@@ -60,11 +62,11 @@ In this monorepo, `npm run config:init` / `config:migrate` / `config:reinit` / `
60
62
  ## Subpath imports
61
63
 
62
64
  ```js
65
+ import eslintAstro from '@st1ggy/linter-config/eslint-astro'
63
66
  import eslintReact from '@st1ggy/linter-config/eslint-react'
64
67
  import eslintSolid from '@st1ggy/linter-config/eslint-solid'
65
- import eslintAstro from '@st1ggy/linter-config/eslint-astro'
66
- import prettierCommon from '@st1ggy/linter-config/prettier-common'
67
68
  import prettierAstro from '@st1ggy/linter-config/prettier-astro'
69
+ import prettierCommon from '@st1ggy/linter-config/prettier-common'
68
70
  import stylelintScss from '@st1ggy/linter-config/stylelint-scss'
69
71
  ```
70
72
 
@@ -93,20 +95,25 @@ If you previously used Stylelint 16 with this preset, upgrade the consumer to **
93
95
 
94
96
  ## Oxlint variants
95
97
 
96
- Each existing stack has an Oxlint counterpart. The new configs are objects typed as `OxlintConfig`; the existing ESLint configs remain flat-config arrays.
98
+ Each existing stack has an Oxlint counterpart. Angular, Vue and Nuxt have additional Ox presets. Oxlint configs are objects typed as `OxlintConfig`. All nine run with Oxlint + Oxfmt; Stylelint remains the CSS/SCSS rule tool. The old `eslint-*-ox` flat-config arrays remain optional compatibility exports, not part of the generated workflow.
99
+
100
+ All imports below are subpaths of `@st1ggy/linter-config`.
97
101
 
98
- | Stack flag | Config import | Formatter | Stylelint |
99
- | ------------- | --------------------------------- | ----------------- | ---------------- |
100
- | `--common-ox` | `@st1ggy/linter-config/common-ox` | `oxfmt-common` | `stylelint-scss` |
101
- | `--react-ox` | `@st1ggy/linter-config/react-ox` | `oxfmt-common` | `stylelint-scss` |
102
- | `--solid-ox` | `@st1ggy/linter-config/solid-ox` | `oxfmt-common` | `stylelint-scss` |
103
- | `--next-ox` | `@st1ggy/linter-config/next-ox` | `oxfmt-common` | `stylelint-scss` |
104
- | `--svelte-ox` | `@st1ggy/linter-config/svelte-ox` | `prettier-svelte` | `stylelint-scss` |
105
- | `--astro-ox` | `@st1ggy/linter-config/astro-ox` | `prettier-astro` | `stylelint-scss` |
102
+ | Stack flag | Oxlint preset | Formatter | Optional compatibility export |
103
+ | -------------- | ------------- | --------------- | ----------------------------- |
104
+ | `--common-ox` | `common-ox` | `oxfmt-common` | — |
105
+ | `--react-ox` | `react-ox` | `oxfmt-common` | — |
106
+ | `--solid-ox` | `solid-ox` | `oxfmt-common` | — |
107
+ | `--next-ox` | `next-ox` | `oxfmt-common` | — |
108
+ | `--svelte-ox` | `svelte-ox` | `oxfmt-svelte` | `eslint-svelte-ox` |
109
+ | `--astro-ox` | `astro-ox` | `oxfmt-astro` | `eslint-astro-ox` |
110
+ | `--angular-ox` | `angular-ox` | `oxfmt-angular` | `eslint-angular-ox` |
111
+ | `--vue-ox` | `vue-ox` | `oxfmt-common` | `eslint-vue-ox` |
112
+ | `--nuxt-ox` | `nuxt-ox` | `oxfmt-common` | `eslint-nuxt-ox` |
106
113
 
107
114
  ### Install and run
108
115
 
109
- The checked engine versions are **Oxlint 1.86.0**, **oxlint-tsgolint 7.0.2003**, and **Oxfmt 0.71.0**, with native TypeScript 7 typed analysis. Use **Node.js 24.16.0+**. JS-plugin compatibility and the rule inventory are checked against these versions; the CLI installs the selected engines with exact versions.
116
+ The checked engine versions are **Oxlint 1.90.0**, **oxlint-tsgolint 7.0.2005**, and **Oxfmt 0.75.0**. The project compiler remains **TypeScript 6.0.3** (the latest stable 6.x); no TypeScript 7 compiler is installed. Use a supported **Node.js LTS** release, minimum **24.16.0**. The CLI installs engines with exact versions and only the selected script/formatter integrations, never ESLint or template parsers for Ox stacks. Svelte Ox formatting requires **Svelte 5**; Svelte 4 projects need an explicitly compatible older lint/format toolchain or an intentional runtime upgrade. This Ox stack does not upgrade an installed Svelte 4 runtime for you. Astro formatting additionally needs **`@astrojs/compiler-rs@^0.5.2`**, installed by the wizard.
110
117
 
111
118
  ```bash
112
119
  npx @st1ggy/linter-config init --solid-ox
@@ -116,7 +123,7 @@ For manual Solid installation:
116
123
 
117
124
  ```bash
118
125
  npm i -D @st1ggy/linter-config eslint-plugin-solid
119
- npm i -D --save-exact oxlint@1.86.0 oxlint-tsgolint@7.0.2003 oxfmt@0.71.0
126
+ npm i -D --save-exact oxlint@1.90.0 oxlint-tsgolint@7.0.2005 oxfmt@0.75.0
120
127
  ```
121
128
 
122
129
  ```ts
@@ -139,7 +146,7 @@ npx oxlint --fix .
139
146
  npx oxfmt --write .
140
147
  ```
141
148
 
142
- Oxlint auto-discovers `oxlint.config.ts` and the applicable `tsconfig.json`. Remove options deleted in TypeScript 7, including `baseUrl`; make `paths` relative to the config instead. For Solid JSX, use `"jsx": "preserve"` and `"jsxImportSource": "solid-js"`. The wizard writes wrappers and installs integrations; it does not edit your tsconfig or package scripts.
149
+ Oxlint auto-discovers `oxlint.config.ts` and the applicable `tsconfig.json`. The project stays on TypeScript 6; do not migrate it to TypeScript 7 for this preset. Oxlint's bundled native typed-lint engine has its own configuration constraints: for example, it does not support `baseUrl`. If your TS6 project relies on such options, evaluate a separate Oxlint tsconfig or keep ESLint typed linting rather than changing the project's compiler. For Solid JSX, use `"jsx": "preserve"` and `"jsxImportSource": "solid-js"`. The wizard writes wrappers and installs integrations; it does not edit your tsconfig or package scripts.
143
150
 
144
151
  When composing configs, specify `typeAware` at the **consumer root**; root-only options are not inherited through `extends`:
145
152
 
@@ -156,9 +163,9 @@ export default defineConfig({
156
163
 
157
164
  ### Oxfmt formatting
158
165
 
159
- `common-ox`, `react-ox`, `solid-ox` and `next-ox` use Oxfmt for formatting. Their lint configs do not load `eslint-plugin-prettier` or execute `prettier/prettier`; run the formatter check alongside linting in CI. The generated `oxfmt.config.ts` imports `@st1ggy/linter-config/oxfmt-common` and is discovered automatically.
166
+ Every Ox stack uses Oxfmt for formatting. Oxlint does not run `prettier/prettier`; run the formatter check alongside linting in CI. The generated `oxfmt.config.ts` imports the stack's formatter preset and is discovered automatically. Svelte/Astro explicitly enable their formatter integrations; Angular associates all `*.html` files with `angular-html`, including templates without a `.component.html` suffix. Vue/Nuxt files are recognized automatically.
160
167
 
161
- The shared config preserves the common style: 120-column width, two-space indentation, single quotes, no semicolons, trailing commas, LF and a final newline. **Import sorting and package.json sorting are explicitly disabled**; the current import lint rules retain control of import order. `.gitignore` and `.prettierignore` are respected during directory traversal. Oxfmt can format an explicitly named gitignored file; for deliberate exclusions, use `.prettierignore` or `ignorePatterns`.
168
+ The shared config preserves the common style: 120-column width, two-space indentation, single quotes, no semicolons, trailing commas, LF and a final newline. **Oxfmt owns import declaration sorting**: external/builtin imports, internal aliases (`@/`, `~/`), parent imports, sibling/index imports, then type imports, with empty lines between groups. Comments preserve explicit sorting partitions; empty lines alone do not. `sortSideEffects: false` preserves the relative order of bare side-effect imports, but they are not barriers by themselves: value imports can move across them. Separate order-sensitive sections with comments, or disable `sortImports` for those files. Oxfmt 0.75 cannot combine empty-line partitions with automatic empty lines between groups. Native `sort-imports` still sorts named specifiers, which Oxfmt 0.75 does not sort; `import-x/newline-after-import` retains the gap after imports. The competing `import-x/order` lint fixer is not executed in Ox stacks. Package.json property sorting stays disabled. `.gitignore` and `.prettierignore` are respected during directory traversal. Oxfmt can format an explicitly named gitignored file; for deliberate exclusions, use `.prettierignore` or `ignorePatterns`.
162
169
 
163
170
  Override options by spreading the shared object:
164
171
 
@@ -172,33 +179,84 @@ export default defineConfig({
172
179
  })
173
180
  ```
174
181
 
175
- `init` keeps an existing `prettier.config.js`; use `migrate` to offer it for removal when switching to Oxfmt. The wizard does not update consumer package scripts. A typical script pair is `"lint": "oxlint ."` and `"format:check": "oxfmt --check ."`.
182
+ `init` preserves existing configs, including custom ESLint companions and old Prettier wrappers. Use `migrate` to overwrite wrappers and offer the old formatter config for removal. The wizard does not update consumer package scripts.
183
+
184
+ For every Ox stack, use `"lint": "oxlint ."` and `"format:check": "oxfmt --check ."`:
185
+
186
+ ```bash
187
+ npx oxlint .
188
+ npx oxfmt --check .
189
+ ```
190
+
191
+ Run `oxlint --fix .` before `oxfmt --write .`. This workflow intentionally has no template linting. Oxfmt delegates framework formatting to bundled Prettier integrations; formatting is not template validation. This is also not a claim that every rule is Rust-native: compatible JS plugins run inside Oxlint. ESLint remains a dependency for the legacy exports and some plugin APIs, but is not a second required command. The original ESLint stacks retain their Prettier workflow.
192
+
193
+ ### Framework coverage
176
194
 
177
- Svelte/Astro and the original ESLint stacks keep their existing Prettier configs and plugins. Stylelint remains the style-rule tool for every stack. Prettier also remains a dependency for those integrations and this repository's generation/legacy checks.
195
+ - **Svelte:** Oxlint checks extracted scripts and supported rune/module rules, not template directives or accessibility. Include `.svelte` files in the consumer tsconfig. SvelteKit aliases from the existing Svelte preset are retained.
196
+ - **Astro:** Oxlint checks frontmatter and browser scripts, including the existing six frontmatter adapters, not template directives or accessibility. Extracted scripts cannot distinguish every frontmatter/browser context.
197
+ - **Vue 3:** the common Ox preset supplies JS/TS checks and 36 native Vue rules from the upstream recommended intersection. Templates, including `v-for` key checks, are not linted. Bindings used only in templates are not treated as unused by script-only checks.
198
+ - **Nuxt:** builds on Vue and adds the four `@nuxt/eslint-plugin` rules through Oxlint's JS-plugin API. `.nuxt` and `.output` are ignored. This is a standalone preset, not the project-aware `@nuxt/eslint` module: generate Nuxt's types/config (`nuxt prepare`) before typed linting and use the application's tsconfig. It does not discover arbitrary auto-import globals from a Nuxt build.
199
+ - **Angular:** the common Ox preset supplies JS/TS checks; 12 `angular-eslint` 22 recommended script rules run as a JS plugin. Neither external HTML nor inline `@Component` templates receive template/accessibility lint checks. The wizard does not install or upgrade the application's Angular runtime. New framework integrations are tested independently of the six source-derived migration inventories.
178
200
 
179
201
  ### Rule coverage
180
202
 
181
- The presets carry over native rule equivalents and compatible JS plugins, including custom severity, options, JSX style, import ordering and syntax restrictions. All default Oxlint categories are disabled; only migrated rules are enabled. Type-aware checks run through **tsgolint/TS7**. TS6 remains a library dependency for existing ESLint presets and some JS plugins; the new consumer command does not launch ESLint or create a TS6 type-checking Program.
203
+ The source-derived presets carry over native rule equivalents and compatible JS plugins, including custom severity, options, JSX style and syntax restrictions; import ordering is intentionally delegated to Oxfmt. All default Oxlint categories are disabled; presets explicitly select rules. Type-aware Oxlint checks run through **tsgolint**, which embeds a native TypeScript-derived engine independently of the project's **TypeScript 6** compiler. Its 7.x package version does not upgrade the project compiler. Oxlint does not provide a TypeScript Program to JS plugins.
182
204
 
183
205
  These are **maximum-feasible migrations, with documented gaps**, rather than fully equivalent replacements:
184
206
 
185
- - **Svelte/Astro:** Oxlint checks extracted scripts, not templates. Template-only checks and TS parser-service-dependent JS rules are unavailable. Checks that would misreport template-used variables are omitted for those scopes. Svelte script/module rules and aliases are retained where supported.
186
- - **Astro:** six frontmatter-only script checks are preserved via an adapter (deprecated Astro APIs, deprecated `getEntryBySlug`, component exports and prerender location). Template directives are not checked. The plugin API cannot distinguish frontmatter from a browser script containing identical text; that ambiguity is recorded as partial coverage.
207
+ - **Svelte/Astro/Vue/Nuxt/Angular:** templates are not linted by this workflow. The retained `eslint-*-ox` exports require explicit setup and their optional framework/template parser packages if you choose to restore such checks. Checks that would misreport template-used variables are omitted from script-only analysis.
208
+ - **Astro:** the Oxlint plugin API cannot distinguish frontmatter from a browser script containing identical text; that ambiguity remains recorded as partial coverage.
187
209
  - Some native implementations have narrower behavior or lack source options. The original JS rule is used where compatible; remaining differences are recorded individually.
188
210
  - Compiler configuration-dependent guards are kept, but default-configuration control fixtures do not count as positive violation evidence.
189
211
  - Existing `eslint-disable` directives do not automatically retain their meaning after rule namespaces change. Use Oxlint directives with the migrated IDs and check `--report-unused-disable-directives` when migrating.
190
212
 
191
- See [the generated rule mapping](docs/OXLINT_RULE_MAPPING.md) for counts and every partial/unsupported mapping. The migrated formatting check is accounted for with status `formatter`, not silently disabled. The full source scopes, rule options and evidence references are in `data/oxlint-*.json`; development tests keep paired source/target fixtures outside the published tarball.
213
+ See [the generated rule mapping](docs/OXLINT_RULE_MAPPING.md) for the six source-derived presets' counts and partial/unsupported mappings. Angular/Vue/Nuxt compose the common preset and add separately tested integrations; they are not claimed to have full source/target rule parity. The migrated formatting check is accounted for with status `formatter`, not silently disabled. The full source scopes, rule options and evidence references are in `data/oxlint-*.json`; development tests keep paired source/target fixtures outside the published tarball.
192
214
 
193
- ### Migration (v8: native formatter)
215
+ ### Migration to the all-Ox formatter workflow
194
216
 
195
- `common-ox`, `react-ox`, `solid-ox` and `next-ox` use Oxfmt instead of Prettier. Their Oxlint command no longer checks formatting. To upgrade a consumer from v7:
217
+ All Ox stacks use Oxfmt instead of a separate Prettier command. To upgrade an existing consumer:
196
218
 
197
- 1. Run the wizard with `migrate --<stack>-ox` and select the old formatter config for removal, or install `oxfmt@0.71.0` and create `oxfmt.config.ts` importing `@st1ggy/linter-config/oxfmt-common` manually.
219
+ 1. Run the wizard with `migrate --<stack>-ox`; review config replacements and select the old formatter config for removal. It installs the checked engine pins and selected integrations. Use the stack-specific formatter import from the table above when configuring manually.
198
220
  2. Add `oxfmt --check .` alongside `oxlint .` in CI; replace the old `prettier --check .` command for that stack.
199
- 3. Run `oxlint --fix .` followed by `oxfmt --write .` when applying fixes, and review consumer-specific formatter overrides.
221
+ 3. Remove `eslint .` from the Ox stack's package scripts. Existing ESLint files are preserved by both `init` and `migrate`; explicitly select old configs for removal if no longer needed. This intentionally drops template lint checks.
222
+ 4. Run `oxlint --fix .`, then `oxfmt --write .`; review consumer-specific formatter overrides.
200
223
 
201
- Svelte/Astro Oxlint stacks and the original ESLint stacks retain their Prettier workflow.
224
+ The original non-Ox ESLint stacks retain their Prettier workflow. No companion ESLint file is generated by an Ox stack, including on `migrate`.
225
+
226
+ ### Curated quality checks
227
+
228
+ The base rules now reject unhandled/misused Promises, awaiting non-thenables, and loose equality (except intentional `== null`). Unnecessary assertions/type parameters, nullish coalescing for nullable objects, early returns and nesting beyond four levels start as warnings. Typed checks require an included tsconfig; `prefer-nullish-coalescing` requires `strictNullChecks`. Primitive fallbacks (`""`, `0`, `false`) are deliberately ignored by that rule so intentional `||` behavior is retained. Review fixes before applying them.
229
+
230
+ Deprecated `newline-before-return` and `jsx-props-no-multi-spaces` are disabled; existing statement-padding rules and Oxfmt retain their relevant layout responsibilities. `unicorn/name-replacements`, `unicorn/consistent-destructuring` and `unicorn/no-unused-properties` are off by default. They can be explicitly enabled in a consumer override as `unicorn-js/name-replacements`, `unicorn-js/consistent-destructuring` and `unicorn-js/no-unused-properties` for a stricter style. The experimental `prefer-optional-chain` and `no-unnecessary-condition` checks remain off.
231
+
232
+ Append strict overrides after the generated ones; a root-level rule can otherwise be overridden by a file profile:
233
+
234
+ ```ts
235
+ import config from '@st1ggy/linter-config/common-ox'
236
+
237
+ export default {
238
+ ...config,
239
+ overrides: [
240
+ ...config.overrides,
241
+ {
242
+ files: ['**/*.{js,jsx,ts,tsx,mts,cts,mjs,cjs}'],
243
+ rules: {
244
+ 'unicorn-js/name-replacements': 'warn',
245
+ 'unicorn-js/consistent-destructuring': 'warn',
246
+ 'unicorn-js/no-unused-properties': 'warn',
247
+ },
248
+ },
249
+ ],
250
+ }
251
+ ```
252
+
253
+ ### React and Next rule migration (v8)
254
+
255
+ React/Next presets now use `@eslint-react/eslint-plugin` instead of `eslint-plugin-react`, including their Oxlint adapters. The modern recommended preset adds React 19 migration, server-function, DOM safety and effect-cleanup checks. The official `eslint-plugin-react-hooks` remains responsible for hooks; overlapping modern-plugin aliases are disabled to avoid duplicate diagnostics.
256
+
257
+ Retained custom checks include button types, `useState` destructuring/naming, unstable context values, useless fragments, and component display names. Self-closing JSX moves to `@stylistic/jsx-self-closing-comp`. Similar modern rules are not guaranteed to report exactly the same cases or severities as their legacy counterparts; the generated [rule mapping](docs/OXLINT_RULE_MAPPING.md) records the active configuration.
258
+
259
+ The legacy checks for `propTypes`/`defaultProps`, boolean-prop naming, prop destructuring, arrow-only component definitions, boolean-value and fragment shorthand, handler naming, and one-component-per-file are no longer enforced. Legacy `jsx-no-leaked-render` is also removed: the modern type-checked conditional-rendering check is not enabled by the selected recommended preset. Legacy JSX undefined-name, duplicate-prop, unescaped-entity, target-blank and deprecated-API diagnostics are not retained as an identical rule set; use TypeScript and explicitly configured project rules where needed. This is a deliberate rule-set change, not a compatibility-preserving plugin rename.
202
260
 
203
261
  ### Migration (v7)
204
262
 
@@ -210,7 +268,9 @@ Svelte/Astro Oxlint stacks and the original ESLint stacks retain their Prettier
210
268
 
211
269
  ### Development of this package
212
270
 
213
- `npm install` uses [`.npmrc`](.npmrc) `legacy-peer-deps=true` (see earlier notes on `eslint-import-resolver-custom-alias`).
271
+ Installs use [`.npmrc`](.npmrc) `strict-peer-deps=true`; no legacy peer-resolution bypass is required. Import aliases use the TypeScript resolver and do not require the old `eslint-import-resolver-custom-alias` or `eslint-plugin-import`. Astro's optional accessibility integration uses `eslint-plugin-jsx-a11y-x`, which declares ESLint 10 support.
272
+
273
+ Security audit is not yet clean: [GHSA-g3hv-75wg-m249](https://github.com/advisories/GHSA-g3hv-75wg-m249) affects the transitive `minimatch` v3/v10 releases required by ESLint, TypeScript ESLint, import/accessibility/Sonar plugins, and `doiuse → multimatch`. These ranges do not admit the fixed v11 release. Updating pnpm removes the previous high-severity findings, but eliminating the remaining moderate findings requires upstream-compatible fixes or separately reviewed backports. A blanket major-version override is intentionally not used; root overrides would not protect consumers of the published config either.
214
274
 
215
275
  **Publishing:** this repo’s **root** `package.json` is the published `@st1ggy/linter-config`:
216
276
 
@@ -224,7 +284,7 @@ Releases are started manually from `Actions` → `Release` → `Run workflow`. I
224
284
 
225
285
  ## Toolchain (this repo)
226
286
 
227
- The `CI` GitHub Actions workflow runs linting, the original Solid tests, Oxlint/Oxfmt tests, explicit TS6 and native TS7 checks, inventory/generated-config checks, and packed-package smoke tests on pushes to `main` and pull requests. It checks Node.js `24.16.0` and `latest`, and installs tarballs with npm and isolated pnpm. A separate `format:ox:check` validates formatting with Oxfmt. The `Release` workflow runs these checks before publishing as well.
287
+ The `CI` GitHub Actions workflow runs linting, the original Solid tests, Oxlint/Oxfmt tests, TypeScript 6 compiler/declaration checks, inventory/generated-config checks, and packed-package smoke tests on pushes to `main` and pull requests. It checks Node.js `24.16.0` and `lts/*` (latest LTS, not Current), and installs tarballs with npm and isolated pnpm. A separate `format:ox:check` validates formatting with Oxfmt. The `Release` workflow uses the latest Node.js LTS and runs these checks before publishing as well.
228
288
 
229
289
  There is **one** published package at the **repository root** (no `packages/` workspace layout).
230
290
 
@@ -246,9 +306,9 @@ npm run lint
246
306
  | `npm run lint:fix` | Auto-fix ESLint, Stylelint, Prettier |
247
307
  | `npm run inventory` | Regenerate [`data/linter-config-inventory.json`](data/linter-config-inventory.json) |
248
308
  | `node --test scripts/solid-config.test.mjs` | Check Solid JSX/TSX linting and wrapper generation |
249
- | `node scripts/package-smoke.mjs` | Check all six packed Oxlint stacks, their CLI/TS7 checks and legacy imports |
309
+ | `node scripts/package-smoke.mjs` | Check all nine packed Oxlint stacks, their CLI/typed lint checks and legacy imports |
250
310
  | `node scripts/package-smoke.mjs --pm pnpm` | Check the tarball using isolated pnpm dependencies |
251
- | `npm run typecheck:ox` | Explicit native TypeScript 7 compiler check |
311
+ | `npm run typecheck` | TypeScript 6 compiler check |
252
312
  | `npm run test:ox` | Oxlint integration, rule parity and coverage guardrail tests |
253
313
  | `npm run generate:ox` / `generate:ox:check` | Generate/verify the six Oxlint configurations and rule map |
254
314
  | `npm run inventory:ox` / `inventory:ox:check` | Generate/verify source scopes, evidence and coverage reports |
@@ -260,4 +320,4 @@ npm run lint
260
320
 
261
321
  ## Optional ESLint add-ons
262
322
 
263
- You can add **eslint-plugin-n**, **eslint-plugin-jsx-a11y**, **eslint-plugin-perfectionist**, or stricter **typescript-eslint** in your own config if needed.
323
+ You can add **eslint-plugin-n**, **eslint-plugin-jsx-a11y-x**, **eslint-plugin-perfectionist**, or stricter **typescript-eslint** in your own config if needed. Check each integration's ESLint peer range.