doc,loaders,module: clarify hook chain execution sequence

[JakobJingleheimer]

Closes#51876
Closes#51878

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[yklcs]

I'd like to suggest making changes in the "hooks" section too for clarity, as it also mentions chaining. The "subsequent loader" part, in specific.

node/doc/api/module.md

Lines 376 to 380 in 6bb7c4d

	Hooks are part of a chain, even if that chain consists of only one custom
	(user-provided) hook and the default hook, which is always present. Hook
	functions nest: each one must always return a plain object, and chaining happens
	as a result of each function calling `next<hookName>()`, which is a reference to
	the subsequent loader's hook.

[JakobJingleheimer]

I'd like to suggest making changes in the "hooks" section too for clarity, as it also mentions chaining. The "subsequent loader" part, in specific.

Hmm, here I'm not seeing the confusing bit. Do you mean you'd like some indication of which loader will be in next<hookName>? I wouldn't want to be too repetitive, so how about something simple, like:

- which is a reference to the subsequent loader's hook.+ which is a reference to the subsequent loader's hook (in LIFO order).

[yklcs]

I'd like to suggest making changes in the "hooks" section too for clarity, as it also mentions chaining. The "subsequent loader" part, in specific.

Hmm, here I'm not seeing the confusing bit here. Do you mean you'd like some indication of which loader will be in next<hookName>? I wouldn't want to be too repetitive, so how about something simple, like:

- which is a reference to the subsequent loader's hook.+ which is a reference to the subsequent loader's hook (in LIFO order).

I think that would help, maybe along with a link to #chaining?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/57541/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/57548/

[nodejs-github-bot]

Landed in 2e2a848