react-doctor 0.9.2-dev.b1352a2 → 0.9.2-dev.bf470d5

package/dist/index.d.ts

@@ -1,4 +1,4 @@
-import { FrameworkToken } from "oxlint-plugin-react-doctor";
+import { FrameworkToken } from "oxlint-plugin-react-doctor/core";
 
 //#region ../../node_modules/.pnpm/effect@4.0.0-beta.70/node_modules/effect/dist/Types.d.ts
 /**
@@ -9333,11 +9333,17 @@ interface ReactDoctorConfig {
    * Entries resolve exactly like `--project` values: workspace package
    * names (or directory basenames) first, then directory paths relative to
    * the scanned root. `"*"` selects every discovered workspace project.
-   * Invalid entries fail the run with the same error as the flag.
+   * Invalid entries fail the run with the same error as the flag — except
+   * under `--staged`, where they warn and fall back to a single scan at the
+   * root, because `--staged` runs in a commit hook and a stale entry there
+   * would block every commit.
    *
    * Precedence: an explicit `--project` flag overrides this list. Only the
    * config at the invocation root is consulted — `projects` inside a
-   * module's own config is ignored (modules can't redirect the scan).
+   * module's own config is ignored (modules can't redirect the scan). Under
+   * `--staged` this list applies only when you invoke react-doctor from the
+   * directory that declared it, so a per-package or positional run does not
+   * resolve an ancestor's entries against the package.
    */
   projects?: string[];
   textComponents?: string[];