react-render-detective 0.3.0 → 0.5.0

package/dist/core.d.cts

@@ -15,6 +15,8 @@ interface Lifecycle {
     unmounts: number;
     /** Mounts that followed an unmount of the same component. */
     remounts: number;
+    /** When the most recent remount was observed. */
+    lastRemountAt?: number;
 }
 interface NodeRecord {
     id: string;
@@ -118,6 +120,16 @@ declare class Detective {
      */
     inlineDefinitionSuspected(name: string): boolean;
     lifecycleOf(name: string): Lifecycle;
+    /**
+     * Did a whole-tree rebuild just happen?
+     *
+     * Hot reload is the most common cause of remounts in development, and this
+     * tool only ever runs in development — so without this it would confidently
+     * blame a `key` every time React Fast Refresh replaced a module. A real key
+     * or inline-definition problem affects one component; a reload affects many
+     * at once.
+     */
+    private reloadSuspectedAt;
     /** Hot path. Must stay allocation-free and O(1). */
     recordAttempt(node: NodeRecord, props: Record<string, unknown>): void;
     recordStateChange(node: NodeRecord, change: TrackedStateChange): void;
@@ -196,6 +208,8 @@ interface DiagnosisInput {
     remounts: number;
     /** The component looks like it is declared inside another component's render body. */
     inlineDefinitionSuspected: boolean;
+    /** Many components remounted at once — a hot reload or a route change. */
+    treeReloadSuspected: boolean;
     selfDuration: number;
     attempts: number;
     committed: boolean;

package/dist/core.d.ts

@@ -15,6 +15,8 @@ interface Lifecycle {
     unmounts: number;
     /** Mounts that followed an unmount of the same component. */
     remounts: number;
+    /** When the most recent remount was observed. */
+    lastRemountAt?: number;
 }
 interface NodeRecord {
     id: string;
@@ -118,6 +120,16 @@ declare class Detective {
      */
     inlineDefinitionSuspected(name: string): boolean;
     lifecycleOf(name: string): Lifecycle;
+    /**
+     * Did a whole-tree rebuild just happen?
+     *
+     * Hot reload is the most common cause of remounts in development, and this
+     * tool only ever runs in development — so without this it would confidently
+     * blame a `key` every time React Fast Refresh replaced a module. A real key
+     * or inline-definition problem affects one component; a reload affects many
+     * at once.
+     */
+    private reloadSuspectedAt;
     /** Hot path. Must stay allocation-free and O(1). */
     recordAttempt(node: NodeRecord, props: Record<string, unknown>): void;
     recordStateChange(node: NodeRecord, change: TrackedStateChange): void;
@@ -196,6 +208,8 @@ interface DiagnosisInput {
     remounts: number;
     /** The component looks like it is declared inside another component's render body. */
     inlineDefinitionSuspected: boolean;
+    /** Many components remounted at once — a hot reload or a route change. */
+    treeReloadSuspected: boolean;
     selfDuration: number;
     attempts: number;
     committed: boolean;

package/dist/core.js

@@ -1,3 +1,3 @@
-export { Detective, RingBuffer, defaultConfig, detectDev, diagnose, diffProps, formatInspected, getDetective, inspect, isPlainObject, isReactElement, matches, mergeConfig, severityFor, shallowEqual, shouldInstrument, valueType } from './chunk-QOGTEVBP.js';
+export { Detective, RingBuffer, defaultConfig, detectDev, diagnose, diffProps, formatInspected, getDetective, inspect, isPlainObject, isReactElement, matches, mergeConfig, severityFor, shallowEqual, shouldInstrument, valueType } from './chunk-DI5STJM4.js';
 //# sourceMappingURL=core.js.map
 //# sourceMappingURL=core.js.map