René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`enabledHooksExist()` doesn't work as intended","articleBody":"I took a look at `enabledHooksExist()`, but as discussed in https://github.com/nodejs/node/pull/59873#issuecomment-3304866589 and https://github.com/nodejs/node/pull/60913, it seems to not work as intended at the moment:\r\n\r\n\u003e Following the suggestion to use enabledHooksExist(), I spent quite some time on it and gave that a try—but found that it consistently returned true, even when no async hooks were active. So, I reverted to using getHookArrays()[0].length \u003e 0, as it provides a more accurate reflection of the current hook state.\r\n\r\n---\r\n\r\n`enabledHooksExist()` checks `async_hook_fields[kCheck] \u003e 0`, but `kCheck` is intentionally set to `1` at Node.js startup, even when no user async hooks have been registered:\r\n\r\nFrom env.cc (L1763):\r\n\r\nhttps://github.com/nodejs/node/blob/e28656a6172c35d88a472e33894a11f0e9f98eee/src/env.cc#L1748-L1763\r\n\r\nThis means `enabledHooksExist()` **always** returns `true`, regardless of whether any `AsyncHook` instances have actually been created and enabled by user code.\r\n\r\n---\r\n\r\nThis behavior dates back to PR #15454 it seems, but even after going through that discussion, I don't really understand the reasoning behind it and the TODO that says we should revert this for LTS releases. I feel like `fields_[kCheck]` should instead be set to `0` during initialization.\r\n\r\nShould we just change that or add a new helper function that would essentially do `AsyncContextFrame.current() != null || getHookArrays()[0].length \u003e 0`?","author":{"url":"https://github.com/gurgunday","@type":"Person","name":"gurgunday"},"datePublished":"2025-12-10T21:46:47.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/61019/node/issues/61019"}