[Feature] support createRequire

[loynoir]

import { createRequire } from 'module'
const require = createRequire(import.meta.url)

/**
 * @type {typeof ReadableStream}
 */
let RS: typeof ReadableStream
if (typeof ReadableStream !== 'undefined') {
  RS = ReadableStream
} else {
  try {
    RS = require('node:stream/web').ReadableStream
  } catch {
    RS = require('web-streams-polyfill/dist/ponyfill.js').ReadableStream
  }
}

export default RS

$ esbuild --bundle XXX.mts
The package "module" wasn't found on the file system but is built into node. Are you trying to
bundle for node? You can use "--platform=node" to do that, which will remove this error.

$ esbuild src/index.mts --bundle --platform=node
... web-streams-polyfill/dist/ponyfill.js is not bundled ...

$ # remove `createRequire`, let `require` global
web-streams-polyfill/dist/ponyfill.js is bundled

But, reference to a global variable require within ESM, I think it's not in standard?

[evanw]

Do other bundlers support this too? I mainly try to have esbuild follow existing conventions instead of inventing new ones. I don't think esbuild should do something like this without e.g. Webpack doing this too, because I don't want to create new conventions and fragment the community.

[millsp]

It seems this has been implemented in Webpack 30 days ago
webpack/webpack#14228
swc-project/swc#4101

[LZQCN]

#1921 (comment)
This seems to be a temporary solution

[markus-incisive]

I'm currently hijacking the require variable to do this, and it works for my purposes.

/* index.mts */
import { createRequire } from 'node:module'

let foo

try {
  const originalRequire = require
  require = createRequire(__filename)
  foo = require('path/to/foo')
  require = originalRequire
} catch (error) {
  console.error(error)
  process.exit(1)
}