Error message for when there code evaluation is still pending and there are no pending async operations

[tom-sherman]

What is the problem this feature will solve?

Given the following program:

function main() {
  return new Promise(() => {});
}

await main();
console.log("hello");

Node.js exits the process immediately, with an error code of 13.

What is the feature you are proposing to solve the problem?

In addition to exiting with a non-zero code, show an error message.

This how deno works. Run the above program with deno run and you get the following error in the console:

error: Module evaluation is still pending but there are no pending ops or dynamic imports. This situation is often caused by unresolved promise.

What alternatives have you considered?

No response

[theanarkh]

What is your Node.js version ? This code(put into test.mjs) works in v16.6.0 and v19.0.0-pre.

[tom-sherman]

@theanarkh What do you mean by works? It's not supposed to work, it exits with an error code (13 - "Unfinished Top-Level Await") for me as documented here: https://nodejs.org/api/process.html#process_exit_codes

I opened this issue to suggest adding a friendly error message along with code to inform users why the program exited without having to google the error code. This is what deno does and it's quite nice.

[F3n67u]

Related issue: nodejs/promises-debugging#16, #43162

[F3n67u]

Duplicate of #42868

[theanarkh]

@theanarkh What do you mean by works? It's not supposed to work, it exits with an error code (13 - "Unfinished Top-Level Await") for me as documented here: https://nodejs.org/api/process.html#process_exit_codes

I opened this issue to suggest adding a friendly error message along with code to inform users why the program exited without having to google the error code. This is what deno does and it's quite nice.

Sorry, i misunderstand it. i supposed what you mean is the process throw a Error and the code is 13.

[F3n67u]

Close it in favor of #42868