@useinsider/eslint-config 4.0.0-beta.2 → 4.0.0-beta.3

package/README.md

@@ -127,8 +127,8 @@ type-checks those files, you are not asked at all. That edit is surgical —
 comments, key order and indentation survive — and declining it prints the exact
 snippet to paste.
 
-To migrate an existing v1 `eslint.config.{js,mjs,cjs}` or a legacy
-`.eslintrc.{js,cjs}`:
+To migrate an existing `eslint.config.{js,mjs,cjs}` — v3's scope-keyed call or
+v1's `useInsider({ preset, config })` — or a legacy `.eslintrc.{js,cjs}`:
 
 ```bash
 npx @useinsider/eslint-config migrate [path]
@@ -137,11 +137,25 @@ npx @useinsider/eslint-config migrate [path]
 The migrate flow auto-detects the source format, prints a summary plus any
 dropped custom rules, asks for confirmation, then splits the config into the
 three-file layout: the `useInsider()` call moves into `insider.lint.*` and
-both linter configs become thin re-exports. Legacy `.eslintrc.{js,cjs}` is
-also handled (custom rules and non-`@useinsider/eslint-config/*` extends are
-dropped with a loud warning so you can review what changed). Legacy
-`.eslintrc.{json,yml,yaml}` are not supported in this release — convert them
-to `.eslintrc.{js,cjs}` first.
+both linter configs become thin re-exports.
+
+A **v3** config takes the shorter route. v4 accepts the same options v3 did,
+so the call is re-housed rather than re-rendered: the file is copied into
+`insider.lint.*` byte-for-byte and only the export statement changes to
+`export const { useInsiderESLint, useInsiderOXC } = useInsider({ ... })`. Your
+comments, `satisfies` clauses, computed values and formatting survive. An
+`await` on the call and an array wrapping it are dropped, since `useInsider()`
+is synchronous in v4 and returns the two renderers. Shapes with nowhere to go
+in a lint module are refused by name rather than half-migrated: more than one
+`useInsider()` call, a default export mixing the call with hand-written
+flat-config blocks, a `defineConfig()` wrapper, and a call reached through a
+variable. An `.eslintignore` beside a v3 config is left alone — flat config
+never read it, and the re-housed call is not rewritten to fold it in.
+
+Legacy `.eslintrc.{js,cjs}` is also handled (custom rules and
+non-`@useinsider/eslint-config/*` extends are dropped with a loud warning so
+you can review what changed). Legacy `.eslintrc.{json,yml,yaml}` are not
+supported in this release — convert them to `.eslintrc.{js,cjs}` first.
 
 Migrate also rewrites your source: an `// eslint-disable-next-line <rule>`
 naming a rule oxlint has taken over becomes `// oxlint-disable-next-line