cc @nodejs/modules-active-members; not sure this is something we've previously discussed

would you mind terribly removing the chaining commit? that's a larger thing we have to deal with for all loaders.

@devsnek done. note even in the first commit Loader#_transformSource holds an array rather than an undefined or single function, so once it's possible to have multiple --loader arguments the transformSource will automatically support chaining. Do you want this changed as well?

@guybedford renaming to moduleTransform or maybe transformModuleSource could make sense as this implementation supports ES modules only.

An earlier attempt at this feature allowed resolve hooks to provide a fetchSource property, but this cannot effectively support chained transforms. Keeping fetch and transform separate makes it possible to support multiple --loader options each providing a transform to be run in sequence. I think a fetch hook is a good idea but a separate feature.

I think this needs more abstract design work before we start throwing more hooks in.

I've labeled this "work in progress" but comment or remove that label if it's not appropriate.

I'd prefer a bit more detail in the commit message if possible.

Closing since #30986 is merged.

Oh wow I didn't even know that this PR was here.

@GeoffreyBooth I dropped the ball on this, other priorities unfortunately took over. I really appreciate the effort you took to get the transform hook implemented and merged!