René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Sync `resolve` hook does not affect `require.resolve()`","articleBody":"### Version\n\nv24.14.0\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.26200.0 x64 (Windows 11 25H2 Home Edition build 26200.8037)\n```\n\n### Subsystem\n\nnode:module\n\n### What steps will reproduce the bug?\n\nExtending the code @joyeecheung wrote in her initial PR for `registerHooks` (#55698):\n\n```js\nimport assert from 'node:assert';\nimport { registerHooks, createRequire } from 'node:module';\nimport { writeFileSync } from 'node:fs';\n\nwriteFileSync('./bar.js', 'export const id = 123;', 'utf8');\n\nregisterHooks({\n  resolve(specifier, context, nextResolve) {\n    const replaced = specifier.replace('foo', 'bar');\n    return nextResolve(replaced, context);\n  },\n  load(url, context, nextLoad) {\n    const result = nextLoad(url, context);\n    return {\n      ...result,\n      source: result.source.toString().replace('123', '456'),\n    };\n  },\n});\n\n// Checks that it works with require.\nconst require = createRequire(import.meta.url);\nconst required = require('./foo.js');  // redirected by resolve hook to bar.js\nassert.strictEqual(required.id, 456);  // replaced by load hook to 456\n\n// Checks that it works with import.\nconst imported = await import('./foo.js');  // redirected by resolve hook to bar.js\nassert.strictEqual(imported.id, 456);  // replaced by load hook to 456\n\n// ADDED\nconsole.log(import.meta.resolve('./foo.js'))  // ✅ prints the file: url of bar.js\nconsole.log(require.resolve('./foo.js'))      // 🚫 MODULE_NOT_FOUND ./foo.js\n```\n\n\n### How often does it reproduce? Is there a required condition?\n\nAlways.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThe last `console.log` statement should print the file path of `bar.js`.\n\n### What do you see instead?\n\n`MODULE_NOT_FOUND` thrown.\n\n### Additional information\n\nThis [comment](https://github.com/nodejs/node/pull/55698#issuecomment-2809007734) did notice the bug already but it seems it didn't get any traction.","author":{"url":"https://github.com/Septh","@type":"Person","name":"Septh"},"datePublished":"2026-04-11T13:52:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/62692/node/issues/62692"}