Switching to import is good, but I think removing import/require is bad. Like I said, it's not clear where these methods from.

When I first saw

new URL('file:///C:/path/').pathname;    // Incorrect: /C:/path/
fileURLToPath('file:///C:/path/');       // Correct:   C:\path\ (Windows)

I really don't know how to use fileURLToPath,

• Is it static method of URL? URL.fileURLToPath(...)
• Is it method of URL instance? new URL(...).fileURLToPath()
• Or the correct one import {fileURLToPath} from 'url'
• (edit) Or even it's global ? Like URL

It doesn't make sense to remove these imports. check https://nodejs.org/api/child_process.html, every example has require('child_process') it's very clear how to use it.

worker_threads /fs / assert/dns has those imports as well, I don't think people care much it's import or require

@fisker Fair enough, I've added the require calls back and added ESM examples. Would you like to add ESM examples to #38645?

Yes, with pleasure.

Landed in df744db