react-doctor 0.2.14-dev.09fe1ff → 0.2.14-dev.24425b1

package/dist/index.d.ts

@@ -53,6 +53,14 @@ type RuleSeverityOverride = "error" | "warn" | "off";
  * `rules` and `categories` fields on `ReactDoctorConfig`. Per-rule
  * wins over per-category when both match the same diagnostic.
  */
+/**
+ * Closed set of severity buckets. Spelled out (rather than
+ * `Record<string, …>`) so an unknown/typo'd bucket key is a type error
+ * instead of a silent no-op.
+ */
+interface SeverityBuckets {
+  "compiler-cleanup"?: RuleSeverityOverride;
+}
 interface SurfaceControls {
   /**
    * Tag names whose diagnostics should be force-included on the surface,
@@ -253,6 +261,20 @@ interface ReactDoctorConfig {
    * single category, use `ignore.tags` instead.
    */
   categories?: Record<string, RuleSeverityOverride>;
+  /**
+   * Per-bucket severity map. Buckets are curated rule families with a
+   * shared gating story (not categories). Today the only bucket is
+   * `"compiler-cleanup"`: the redundant-memoization rule
+   * (`react-compiler-no-manual-memoization`) that ships as a warning once
+   * React Compiler is detected. Set it to `"error"` to re-enable strictness.
+   *
+   * ```json
+   * { "buckets": { "compiler-cleanup": "error" } }
+   * ```
+   *
+   * A per-rule override in `rules` still wins over a bucket entry.
+   */
+  buckets?: SeverityBuckets;
   /**
    * User-defined oxlint plugins to load alongside the built-in
    * `react-doctor` plugin. Each entry is either:
@@ -347,6 +369,22 @@ interface ProjectInfo {
    * — no `rn-*` rules load for the project at all.
    */
   hasReactNativeWorkspace: boolean;
+  /**
+   * The declared `expo` package version spec (e.g. `"~51.0.0"`), looked up
+   * in the project or any of its workspace packages, or `null` when `expo`
+   * isn't a dependency. Doubles as react-doctor's "is this an Expo project?"
+   * signal (`expoVersion !== null`) and its SDK-version source — the `expo`
+   * major tracks the Expo SDK release one-to-one — paralleling how
+   * `reactVersion` models the React runtime.
+   *
+   * Keyed off the dependency rather than `framework === "expo"` because
+   * `detectFramework` returns the first matching package, so a project
+   * declaring both `expo` and a web bundler (`vite` / `next`) classifies as
+   * the web framework yet is still an Expo project. Drives the `expo`
+   * capability in `buildCapabilities` (which gates every Expo-specific
+   * rule) and the ported expo-doctor checks.
+   */
+  expoVersion: string | null;
   /**
    * `true` when the project (or any of its workspace packages) declares
    * `react-native-reanimated`. Lets diagnostics surface reanimated's
@@ -704,7 +742,7 @@ interface BuildJsonReportInput {
   totalElapsedMilliseconds: number;
 }
 declare const buildJsonReport: (input: BuildJsonReportInput) => JsonReport; //#endregion
-//#region src/can-oxlint-extend-config.d.ts
+//#region src/build-skipped-checks.d.ts
 //#endregion
 //#region src/get-diff-files.d.ts
 /**