Invalid ES module, internal SyntaxError, error text could use more context

[josh-hemphill]

• Version: v14.11.0
• Platform: Win10 64bit
• Subsystem: internal/modules/esm/translators.js:117:18

What steps will reproduce the bug?

While other async operations are happening, load a malformed ES module

How often does it reproduce? Is there a required condition?

Consistently, in an ES module project, it seems to appear with lots of async operations including some that are using sockets.

What is the expected behavior?

Error: unexpected character at ...

What do you see instead?

(node:26584) UnhandledPromiseRejectionWarning: SyntaxError: Missing initializer in destructuring declaration
    at Loader.moduleStrategy (internal/modules/esm/translators.js:117:18)
    at Loader.moduleStrategy (internal/modules/esm/translators.js:117:18)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

Additional information

Easy recreation:

// Malformed Module testImport.js
const {
	general: { getLocal },
} from '#utils');

// imported asynchronously
import('./testImport.js').catch(err => console.log(err))

Results in

SyntaxError: Missing initializer in destructuring declaration
    at Loader.moduleStrategy (internal/modules/esm/translators.js:117:18)
    at async link (internal/modules/esm/module_job.js:42:21)

In which there's no helpful information about the locations/modules involved

[devsnek]

Can you provide some code?

[devsnek]

So the error message isn't technically wrong (the initializer of const { general: { getLocal } } is missing, there's from "#utils") instead). Can you explain a bit more about what you're expecting to see?

[josh-hemphill]

Yeah, it took me a while to realize that it was correctly referring to my own code, for the longest time I thought it was an issue with a library or something I was using.
It would be nice to have something about where it's taking place, since the stack contains no information about what part of the use code it's coming from, or that it is user code. And that line that's included in the stack contains the URL that's being imported, so just having the the target URL be output would be very helpful.
I had to turn off skipping node_internals to break on the error and extract the URL to know where it was breaking.

[Kamsi-yonna]

I keep seeing this in mine
ERROR missing ) after argument list

at ESMLoader.moduleStrategy (node:internal/modules/esm/translators:119:18)
at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14) at async link (node:internal/modules/esm/module_job:68:21)

I wish I could actually trace where it was coming from.