Repository navigation
doc: point require.extensions users to customization hooks - #67243
adityareddy-dev wants to merge 1 commit into
Conversation
Signed-off-by: Aditya Reddy <82123567+adityareddy-dev@users.noreply.github.com>
|
Review requested:
|
|
Welcome to Node.js, and thank you for your first contribution! Before review, please take a moment to read:
Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal. Caution AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context. |
GeoffreyBooth
left a comment
There was a problem hiding this comment.
This is a good start. We could probably go further and provide migration examples, but that should come in a follow-up.
The
require.extensionsdeprecation doesn't point to supported loading hooks. I linkedmodule.registerHooks()and its synchronous hook guide from the API and deprecation docs.Fixes: #32483