Synchronous exceptions in ES modules are always 'caught'

Version

20.3.1

Platform

Darwin mbp.peet.io 22.6.0 Darwin Kernel Version 22.6.0: Fri Sep 15 13:39:52 PDT 2023; root:xnu-8796.141.3.700.8~1/RELEASE_X86_64 x86_64

Subsystem

inspector

What steps will reproduce the bug?

1. Start a program containing throw new Error('foo'); in an ES module
2. Attach a debugger, like devtools or VS Code's debugger, and enable "pause on uncaught exceptions"
3. Run the program

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

100%

What is the expected behavior? Why is that the expected behavior?

The runtime should pause on the throw line

What do you see instead?

The runtime does not pause and the program exits

Additional information

First reported in https://github.com/microsoft/vscode-js-debug/issues/1861

Guessing this is because module evaluation is in a try/catch. Wonder if there's any machinery that can be used to mark containing exceptions as uncaught

https://github.com/nodejs/node/blob/0a0b8dfd0d3684d6602599e1f0d9d935b3758700/lib/internal/modules/esm/module_job.js#L217-L219

Comienza con lib/internal/modules/esm/module_job.js alrededor de las líneas 217-219 y reproduce el problema usando un módulo ES que contenga un throw síncrono con un depurador adjunto. Sigue cómo el inspector gestiona la excepción durante la evaluación del módulo; se considera terminado cuando el depurador se pausa en el throw al estar habilitado pause on uncaught exceptions.