Node w/ ESM uses CJS files

[revmischa]

Describe the bug

I'm trying to compile my NodeJS app with ESM. When I build with esbuild, it selects the CJS build of Faker instead of the ESM version.

    Checking for a package in the directory "/Users/cyber/dev/platform/node_modules/@faker-js/faker/locale/en_US"
    Read 8 entries for directory "/Users/cyber/dev/platform/node_modules/@faker-js/faker"
    Looking for "./locale/en_US" in "exports" map in "/Users/cyber/dev/platform/node_modules/@faker-js/faker/package.json"
      Checking object path map for "./locale/en_US"
      The key "./locale/*" matched with "en_US" left over
      Checking condition map for one of ["default", "import", "node"]
        The key "node" applies
        Checking path "en_US" against target "./dist/cjs/locale/*.js"
          Substituted "en_US" for "*" in "./dist/cjs/locale/*.js" to get "./dist/cjs/locale/en_US.js"
      The resolved path "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale/en_US.js" is exact
      Read 56 entries for directory "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale"
      Resolved to "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale/en_US.js"
  Read 56 entries for directory "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale"
  Ignoring "/Users/cyber/dev/platform/node_modules/@faker-js/faker/tsconfig.json" because "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale/en_US.js" is inside "node_modules"
  Primary path is "/Users/cyber/dev/platform/node_modules/@faker-js/faker/dist/cjs/locale/en_US.js" in namespace "file"

Reproduction

I'm using esbuild with --bundle --target node14 --mainFields module,main --format esm

Additional Info

I believe the problem is in faker's package.json:

{
"exports": {
    ".": {
      "node": "./dist/cjs/index.js",
      "es2015": "./dist/esm/index.js",
      "default": "./dist/esm/index.js"
    },
    "./locale/*": {
      "node": "./dist/cjs/locale/*.js",
      "es2015": "./dist/esm/locale/*.js",
      "default": "./dist/esm/locale/*.js"
    },
    "./package.json": "./package.json"
  },
}

It appears to assume if I'm using node I want commonjs. I'm using node and I want ESM.
I think it should be using require vs import - see the nodejs docs here https://nodejs.org/api/packages.html#conditional-exports

Then it will select the proper version depending on if the consumer is using require or import. No assumptions needed.