next-leak 0.7.0 → 0.9.0

package/dist/route-guidance.d.ts

@@ -1,4 +1,23 @@
 import type { PrerenderManifest } from "./manifests.js";
+/**
+ * Turns a prerendered value into one that varies per request.
+ *
+ * A value the build already prerendered is the one value guaranteed *not* to
+ * measure anything: every request hits the same warm cache entry and the route
+ * reads as flat no matter what it retains. That is a silent false negative, and
+ * it lands on exactly the leaks being reported now — `use cache`,
+ * `cacheComponents` and ISR all key on the params
+ * (vercel/next.js#97938, #97776, #97424, #92287).
+ *
+ * The prerendered value is still the best hint available: it shows the shape
+ * the app accepts. So the shape is kept and only the tail is made to move —
+ * `post-0` becomes `post-{n}`, `seed` becomes `seed-{n}`.
+ *
+ * If the app answers 404 for params it never prerendered, the run says so
+ * loudly through its non-2xx count. A noisy 404 is a far better outcome than a
+ * quiet `stable`.
+ */
+export declare function varyingValueFrom(prerendered: string): string;
 /**
  * Sample values lifted from paths the build actually prerendered.
  *

package/dist/runner.d.ts

@@ -18,6 +18,28 @@ export type RouteReport = {
     status: "failed";
     reason: string;
 }
+/**
+ * The measured process ran out of heap partway through. This is a verdict,
+ * not a failure: the route did not fit in the limit the run gave it, and the
+ * outcome decides regardless of the shape of the truncated curve — the same
+ * rule the build path applies to a static-generation worker that dies.
+ *
+ * Kept apart from `measured` because there is no after-snapshot and no
+ * complete trend, and dressing it as a full measurement would claim data
+ * that does not exist.
+ */
+ | {
+    route: string;
+    status: "died-of-heap";
+    requestPath: string;
+    reason: string;
+    /** Post-GC readings up to the death; may be as short as the baseline. */
+    memorySamples: HeapSample[];
+    peaks: PeakSample[];
+    cyclesCompleted: number;
+    cyclesRequested: number;
+    requestsPerCycle: number;
+}
 /**
  * The route was reachable, but the load could not have exercised the code
  * path it represents — so no verdict is emitted. Measuring an ISR route

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-leak",
-  "version": "0.7.0",
+  "version": "0.9.0",
   "description": "Find out whether your Next.js app actually leaks memory — how much, on which route, and whose fault it is.",
   "keywords": [
     "nextjs",