From 817133fcab8e9b04d5f072699d34028d9ab3e5e4 Mon Sep 17 00:00:00 2001 From: kovan Date: Wed, 11 Mar 2026 01:40:02 +0100 Subject: [PATCH 1/3] doc: remove outdated Chrome 66 and ndb references from debugger Remove the Chrome 66.0.3345.0 version check (Chrome 66 shipped in 2018), the claim that Chrome DevTools doesn't support debugging worker threads (which uses time-tied language), and the recommendation to use ndb (which has been archived since July 2023). Fixes: https://github.com/nodejs/node/issues/54078 Co-Authored-By: Claude Opus 4.6 --- doc/api/debugger.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/doc/api/debugger.md b/doc/api/debugger.md index 03e9cd9185027e..ce25c927d8ef81 100644 --- a/doc/api/debugger.md +++ b/doc/api/debugger.md @@ -260,13 +260,5 @@ For help, see: https://nodejs.org/en/docs/inspector at the end of the URL is generated on the fly, it varies in different debugging sessions.) -If the Chrome browser is older than 66.0.3345.0, -use `inspector.html` instead of `js_app.html` in the above URL. - -Chrome DevTools doesn't support debugging [worker threads][] yet. -[ndb][] can be used to debug them. - [Chrome DevTools Protocol]: https://chromedevtools.github.io/devtools-protocol/ [`debugger`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/debugger -[ndb]: https://github.com/GoogleChromeLabs/ndb/ -[worker threads]: worker_threads.md From 6f6d86bdf1467a89ef5befcfa29a7d9416557579 Mon Sep 17 00:00:00 2001 From: kovan Date: Wed, 11 Mar 2026 01:40:09 +0100 Subject: [PATCH 2/3] doc: fix URL postMessage example in worker_threads The example claimed that posting a URL object via MessageChannel would print an empty object, but since v21.0.0 (commit d920b7c94b8) it throws a DataCloneError. Update the example and surrounding text to reflect the current behavior. Fixes: https://github.com/nodejs/node/issues/60504 Co-Authored-By: Claude Opus 4.6 --- doc/api/worker_threads.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/doc/api/worker_threads.md b/doc/api/worker_threads.md index 32024e972932cd..a02e8be571a361 100644 --- a/doc/api/worker_threads.md +++ b/doc/api/worker_threads.md @@ -1416,17 +1416,14 @@ port2.postMessage(new Foo()); // Prints: { c: 3 } ``` -This limitation extends to many built-in objects, such as the global `URL` -object: +Some built-in objects cannot be cloned at all. For example, posting a +`URL` object throws a `DataCloneError`: ```js const { port1, port2 } = new MessageChannel(); -port1.onmessage = ({ data }) => console.log(data); - port2.postMessage(new URL('https://example.org')); - -// Prints: { } +// Throws DataCloneError: Cannot clone object of unsupported type. ``` ### `port.hasRef()` From 453df2d6c49aa2598dea862683ef541edb3eec68 Mon Sep 17 00:00:00 2001 From: kovan Date: Wed, 11 Mar 2026 01:40:15 +0100 Subject: [PATCH 3/3] doc: add throwIfNoEntry version history to fs.stat PR #61178 added the throwIfNoEntry option to fs.stat and fsPromises.stat (shipped in v25.7.0) but did not add corresponding YAML version history entries. The sync variants (fs.statSync, fs.lstatSync) already had history entries from PR #33716. Fixes: https://github.com/nodejs/node/issues/62185 Co-Authored-By: Claude Opus 4.6 --- doc/api/fs.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/api/fs.md b/doc/api/fs.md index 66d29bc80fbf18..8481a6458faf45 100644 --- a/doc/api/fs.md +++ b/doc/api/fs.md @@ -1709,6 +1709,10 @@ Removes files and directories (modeled on the standard POSIX `rm` utility).