Repository navigation
Debugger docs: the expired parts ⚰🧹 #54078
Description
Affected URL(s)
https://nodejs.org/docs/latest/api/debugger.html#v8-inspector-integration-for-nodejs
Description of the problem
As of this writing, the final two sentences of the final subsection of the Debugger docs consist of the following two statements:
Chrome DevTools doesn't support debugging worker threads yet.- Good intentions notwithstanding, time phrases tied to the present (e.g: "yet") age like milk.
- Even if the date of writing was known, the assertion itself remains unsourced.
- This unfortunate omission only makes the immediate next step (of Googling about to try and figure out if the purported lack of support is still the case) that much harder.
ndb can be used to debug them.- As of the 28th of July 2023,
ndbhas been archived.
- As of the 28th of July 2023,
How to fix (🤷♂️)
Deleting the final two sentences could perhaps be enough?
On a side note: making the reader aware of the existence of v8.dev (which covers many advanced use cases) could perhaps be of partial service to the goal of documenting the aforementioned advanced use cases. 💡
Activity
rstagi commentedon Jul 28, 2024
There would be an open issue for the Chrome DevTools, which has even been marked as
Won't fix. So I agree it would be best to probably remove any reference to it.ndbcould still be of great value though, maybe it's worth keeping it and just flagging it as deprecated(?)AFAIK, the only alternatives to debug Node.js worker threads effectively are:
Not sure if they're worth mentioning in the docs though 😕
joyeecheung commentedon Jul 30, 2024
I think mentioning VSCode for debugging workers in the docs would be helpful at least. Regarding the Chromium issue it seems to get closed due to inactivity by the bot, they still seem to be open to fix it (on a side note Chromium DevTools team is currently looking into enabling the network tab for Node.js DevTools https://issues.chromium.org/issues/353924015 so supporting Node-specific domains is something they are willing to accept) , just don't have the cycles to prioritize this - if someone submits a CL or starts a design doc or just open a new issue in the Chromium issue tracker, it can get some new momentum going.
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger
doc: remove outdated Chrome 66 and ndb references from debugger