You're welcome. Thanks for the quick merge and release!

It might be worth using resolve’s listing of core modules to default all of them to empty (and override with shims as needed) - then this would have Just Worked.

that sounds like a good idea—we've had a few browserify releases lately that were mostly about adding new empty shims.

(Pull in resolve/lib/core, enumerate the entries, and any key whose value is true is a core module in the current node version)

The set of core modules isn’t the same for all Node versions. We might not necessarily build and run on the same version of Node.

Maybe we need an extra option to specify the target runtime, e.g. —node-version 10.16.0.

@steve-taylor that’s a reasonable addition to resolve if it’s needed; but i do think that building and running on the same version is typical.