next-leak 0.10.0 → 0.10.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -0
- package/THIRD-PARTY-NOTICES.md +1 -1
- package/dist/{chunk-75W2KIXN.js → chunk-OIJE43WX.js} +1138 -1034
- package/dist/cli.js +1 -1
- package/dist/control-client.d.ts +30 -3
- package/dist/index.js +1 -1
- package/dist/ritual.d.ts +7 -0
- package/dist/runner.d.ts +6 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -440,6 +440,17 @@ through the build's source maps.
|
|
|
440
440
|
that is almost nothing. A 1342.9 MB capture of a leaking route parsed 2.4 MB
|
|
441
441
|
of JSON and diffs fine; a 2227.5 MB one whose `strings` section alone was
|
|
442
442
|
868.9 MB is refused, and the message names 869 MB rather than 2227 MB.
|
|
443
|
+
- **A slow snapshot is not a failed route.** `v8.writeHeapSnapshot` blocks the
|
|
444
|
+
measured process until the file is on disk, so the control channel goes
|
|
445
|
+
silent for as long as the write takes — and the worse the leak, the longer
|
|
446
|
+
that is. The wait is judged by bytes reaching disk, not by a clock: a
|
|
447
|
+
snapshot that is still growing is given as long as it needs, while five
|
|
448
|
+
minutes with nothing written is treated as a wedged process and said so. If
|
|
449
|
+
the final snapshot cannot be taken at all, the run keeps its verdict — the
|
|
450
|
+
curve is already complete by then — and reports the missing attribution
|
|
451
|
+
instead of discarding the route. Measured on the
|
|
452
|
+
[#84648](https://github.com/vercel/next.js/issues/84648) reproduction, whose
|
|
453
|
+
4.2 GB capture outlasted every fixed deadline worth setting.
|
|
443
454
|
- **Architectures:** verified on **arm64 and x64** (linux/amd64 in Docker) — same app, same parameters, same verdicts.
|
|
444
455
|
- **Attribution** (naming the file) needs a Turbopack build with server sourcemaps — the Next 15+ default. On webpack builds the registry is empty by design and findings degrade to `unattributed` with raw retainer chains; measurement itself does not depend on it. Note that `output: "standalone"` + `--webpack` produced a bundle that could not start at all on `16.3.0-canary.90` (missing `@swc/helpers`), independently of this tool.
|
|
445
456
|
- Empirically validated on Next **15.5.4, 16.0.x, 16.1.5, 16.2.x, 16.3.0/16.3.1 and 16.3-canary** (incl. Sentry, OpenTelemetry, PPR and i18n apps), against the public reproductions attached to real issues (open and since-fixed). Most recent measurements, 2026-08-17/18: the runtime path on 16.2.12 and 16.3.1-canary.18, the build path on 16.2.12 and 16.3.1. The contracts it relies on are stable since Next 13–14, but older versions are untested.
|