Allow externalized Wasm build about cjs-module-lexer HOT 1 OPEN

Also see the explanation in #94 (comment).

No need for a runtime environment variable at all

There was never one.

We can ALWAYS generate two builds - one with the inlined binary, and one that loads the binary from a separate file

Sounds good to me!
Does this mean that with upstream Node builds, we use the inline binary ones (CJS, not exported in package.json), and load from an external file when loaded as a NPM module (ESM, exported in package.json)?

If this is the case: we'd like to keep a separate script in this repo, to generate a CJS shim for Node to load the builtin from an external NPM module in downstream distro builds.

Also, can I implement this by further stripping on top of #91? To be honest, I'm not a huge fan of @babel/cli and terser here 😅. CI was also broken by the revert.

No environment variable is then needed for the build script at all

An addition optional --without-cjs/esm flag could be nice, but that's not a hard requirement. Please let me know what you think about it.

Only one define variable is needed for WASM_BINARY- whether or not the binary is being generated inline, with the undefined case indicating the external case, unless we absolutely need to customize the external path at build time?

Yes. That would work!

from cjs-module-lexer.