Untracable error messages from beyond short-circuitted load hooks about loaders HOT 3 OPEN

What version of Node.js are you using?

from loaders.

@aduh95 21.1 now when i'm encountering it again.
i'm returning {source,format,shortCircuit} entries from the registered "load" hook for many files, and at some point all i see is:

node:internal/event_target:1084
  process.nextTick(() => { throw err; });
                           ^
SyntaxError [Error]: Unexpected reserved word
    at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:155:18)
    at callTranslator (node:internal/modules/esm/loader:285:14)
    at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:291:30)

Node.js v21.1.0

without context.

A few files get passed forward to the default nextLoad,
and i can't even exclude that one of those throws this,
but i assume in that case the stack trace would report the location of the import due to the call to nextLoad being present in it.
But since a lot of files are being transpiled like this,
i am struggling to come up with a way to re-parse them before the shortCircuit to be able to reproduce the syntax error.
Whatever follows internally after the shortCircuit return, it seems to me that it could catch the parse error from moduleProvider and report something from (or at) the earlier stack along with it.

from loaders.

actually inserting a re-parse/serialization in the load hook to get usable stack trace wasn't a big issue and it solved my problem, but the fact that i have to parse each file an additional time only because there's no way to trace or catch errors from shortCircuits is what seems wasteful.

from loaders.