docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
os-project-manager merged 2 commits into from
Aug 31, 2026
Merged

docs(check-dts-emitted): name the silent worker-death class, not OOM #13898

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b15bcfc
docs(check-dts-emitted): name the silent worker-death class, not OOM
claude Aug 31, 2026
5d42a06
Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…
claude Aug 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
65 changes: 53 additions & 12 deletions scripts/check-dts-emitted.mjs
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
'\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
" settles its promise only on the worker's `message` events - it registers no\n" +
' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
' is the observed one) posts neither "success" nor "error", so the promise never\n' +
' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
' `error` and no `exit` handler. A worker that ends without posting a message\n' +
' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
' settles neither branch, so the promise never settles, the event loop drains,\n' +
' and node exits 0 with the JS pass already written.\n' +
'\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
' Reaching this text is itself evidence the DTS pass exited 0.\n' +
'\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
'\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
'\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
'\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
' A "DTS Build start" with no success and no error line after it is the\n' +
' message-less death above.\n' +
'\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
" package's tsup entries never emit, so every rebuild fails here the same way;\n" +
' line the `types` conditions up with the entry points that are really built.\n' +
'\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
' cache HIT that restores it - clear it with:\n' +
' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
docs(check-dts-emitted): name the silent worker-death class, not OOM#13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

 Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.

Already on GitHub?
Sign in
to your account

 Merged

os-project-manager
merged 2 commits into

from

Aug 31, 2026
 Merged


docs(check-dts-emitted): name the silent worker-death class, not OOM
#13898
 Changes from all commits
Commits

Show all changes


2 commits


Select commit
Hold shift + click to select a range
b15bcfc

docs(check-dts-emitted): name the silent worker-death class, not OOM


claude Aug 31, 2026
5d42a06

Merge remote-tracking branch 'origin/main' into claude/issue-13509-dt…


claude Aug 31, 2026

File filter

Filter by extension
Filter by extension
Conversations

Failed to load comments. 
Loading
Jump to

Jump to file


Failed to load files. 
Loading
 Diff view

 Diff view


65 changes: 53 additions & 12 deletions
scripts/check-dts-emitted.mjs

View file


Open in desktop

Original file line numberDiff line numberDiff line change
Expand Up@@ -25,13 +25,41 @@
// // <- no worker.on('error'), no worker.on('exit')
// });
//
// There is no `error` handler and no `exit` handler. If the worker dies without
// posting a message -- OOM under memory pressure, a hard `process.exit`, a
// terminated thread -- neither branch ever runs, the promise NEVER SETTLES, the
// event loop drains, and **Node exits 0**. tsup's `Promise.all([dtsTask(),
// mainTasks()])` never resolves either, so nothing prints and nothing throws:
// the JS pass has already written `dist/`, so the run leaves a dist with
// `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and reports success.
// There is no `error` handler and no `exit` handler. What that leaves silent is
// a CLASS, not any one trigger: a worker that ends WITHOUT POSTING A MESSAGE and
// without emitting an `error` event -- a hard `process.exit` inside the worker,
// a terminated thread, any other message-less end -- runs neither branch, so the
// promise NEVER SETTLES, the event loop drains, and **Node exits 0**. tsup's
// `Promise.all([dtsTask(), mainTasks()])` never resolves either, so nothing
// prints and nothing throws: the JS pass has already written `dist/`, so the run
// leaves a dist with `index.js` / `index.mjs` / maps and ZERO `.d.ts` files, and
// reports success.
//
// !! OOM IS THE LOUD SIBLING -- IT IS NOT THIS SHAPE. If you got here after a
// memory-starved build, you are looking at a different failure. Node delivers
// worker heap exhaustion as an `error` event (`ERR_WORKER_OUT_OF_MEMORY`), and
// an `error` event with no listener is rethrown by EventEmitter -- so an OOM'd
// DTS pass exits NON-ZERO and prints a stack. A non-zero build is never cached
// by turbo, which is precisely the property this section used to say OOM lacked.
// Measured on Node v22.22.2 / linux x64, against a harness carrying the promise
// shape above (only `message` registered):
//
// worker death mode event process outcome
// ---------------------------------------------------------------------------
// `process.exit()`, CJS caller exit exit 0, ZERO output
// `process.exit()`, ESM caller (top-level exit exit 13 + "unsettled
// await) top-level await" warning
// heap OOM, per-worker `resourceLimits` error exit 1
// heap OOM, process-wide max-old-space error exit 1
//
// Only the first row is the defect this guard closes. The caller's module system
// is load-bearing: the SAME message-less death exits 13 with a warning under an
// ESM top-level `await` and 0 in silence under CJS. tsup's CLI is CJS, which is
// why the shape that was observed was a silent one.
//
// What actually killed the worker in the original observation is NOT established
// here -- only that it ended without an `error` event, because that run exited 0,
// and therefore that memory pressure is not a demonstrated cause of this shape.
//
// That is a correctness problem for the build CACHE, not just for one build.
// `OS_SKIP_DTS` is declared in turbo.json `globalEnv` and it works: measured on
Expand DownExpand Up@@ -165,14 +193,27 @@ function run(dir) {
 ` '${manifest.name ?? ''}'\" - and it reads as though THEIR change broke this package.\n` +
 '\n Most likely cause (#11907): tsup runs DTS generation in a worker thread and\n' +
 " settles its promise only on the worker's `message` events - it registers no\n" +
 ' `error` and no `exit` handler. A worker that dies (OOM under memory pressure\n' +
 ' is the observed one) posts neither "success" nor "error", so the promise never\n' +
 ' settles, the event loop drains, and node exits 0 with the JS already written.\n' +
 ' `error` and no `exit` handler. A worker that ends without posting a message\n' +
 ' AND without an `error` event - a hard `process.exit`, a terminated thread -\n' +
 ' settles neither branch, so the promise never settles, the event loop drains,\n' +
 ' and node exits 0 with the JS pass already written.\n' +
 '\n It is NOT an out-of-memory build, and more heap will not help. Node delivers\n' +
 ' worker heap exhaustion as an `error` event (ERR_WORKER_OUT_OF_MEMORY) which,\n' +
 ' with no listener registered, is rethrown - so an OOM DTS pass exits NON-ZERO\n' +
 ' and prints a stack, the build stops at `tsup`, and this guard never runs.\n' +
 ' Reaching this text is itself evidence the DTS pass exited 0.\n' +
 '\n This guard is what stops that exit 0 from becoming a CACHED artifact: turbo\n' +
 ' caches only successful tasks, and a skip-DTS run already hashes differently,\n' +
 ' so failing here keeps a DTS-less dist from ever being served as a full build.\n' +
 '\n Re-run the build. If it keeps failing here, build with more headroom:\n' +
 ' NODE_OPTIONS=--max-old-space-size=8192 pnpm --filter <pkg> build\n' +
 '\n WHICH SHAPE ARE YOU IN? Count the declarations actually on disk:\n' +
 ' ls dist/*.d.ts dist/*.d.mts dist/*.d.cts 2>/dev/null | wc -l\n' +
 '\n 0 - the DTS pass produced nothing, so read what it printed:\n' +
 ' pnpm --filter <pkg> build 2>&1 | grep -i dts\n' +
 ' A "DTS Build start" with no success and no error line after it is the\n' +
 ' message-less death above.\n' +
 '\n 1 or more - nothing died. package.json promises a declaration path that this\n' +
 " package's tsup entries never emit, so every rebuild fails here the same way;\n" +
 ' line the `types` conditions up with the entry points that are really built.\n' +
 '\n If a poisoned entry was cached before this guard existed, a plain rebuild is a\n' +
 ' cache HIT that restores it - clear it with:\n' +
 ' pnpm exec turbo run build --filter <pkg> --force\n',
Expand Down
Loading