fix: support --print with --input-type=module

[Momena-akhtar]

Description

This PR resolves an inconsistency in the Node.js CLI where the --print (-p) flag did not work properly with ES modules using --input-type=module, making it impossible to use top-level await in quick one-liner scripts.

---

Before this change

node -p "await Promise.resolve(123)" --input-type=module

Output

SyntaxError: await is only valid in async functions and the top level bodies of modules
# OR
Error [ERR_EVAL_ESM_CANNOT_PRINT]: Cannot print result of an ES module evaluation

After this change

node -p "await Promise.resolve(123)" --input-type=module

Output

123

---

What this PR does

• Enables top-level await to work with --print when --input-type=module is used
• Wraps the expression in an async () => (...) IIFE
• Uses a dynamic ES module evaluation via runEntryPointWithESMLoader
• Prints the resolved value to stdout
• Handles execution errors gracefully
• Adds test coverage in test/parallel/test-cli-print-esm.js

---

Test Added

// test/parallel/test-cli-print-esm.js

'use strict';

const { execSync } = require('child_process');
const assert = require('assert');

const output = execSync(
  `${process.execPath} -p "await Promise.resolve(123)" --input-type=module`
).toString().trim();

assert.strictEqual(output, '123');

---

Related

• Fixes: Make --print respect --input-type=module #58994
• Inspired by behavior in Bun (bun -p)
• Related to prior fixes in --eval for ESM

Notes

This is a minimal and safe change that improves consistency and scriptability for developers using ES modules interactively or in pipelines.
Let me know if you'd like to see support extended to TypeScript --input-type=module-typescript as well.

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[jsumners-nr]

This has lost a rather important comment.

[GeoffreyBooth]

See also: #52105

That earlier PR might have some tests that you could port over into this one.