Vite prefers module main field over exports browser field in library package.json

[segevfiner]

Describe the bug

I have a library that defines:

{
  "name": "lib",
  "main": "./node.js",
  "module": "./node.mjs",
  "browser": "./browser.mjs",
  "exports": {
    "browser": "./browser.mjs",
    "import": "./node.mjs",
    "require": "./node.js"
  }
}

Contrary to the docs and expected behavior. Vite picks "module": "./node.mjs" and I get Node ESM printed. According to the docs, and Node.JS behavior, exports should be preferred and used when specified (P.S. Vite AFAIK doesn't use the browser main field).

Reproduction

https://stackblitz.com/edit/vitejs-vite-sh5wuy?file=lib/package.json

System Info

System:
    OS: macOS 12.5.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 135.59 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.17.0 - ~/.nvm/versions/node/v16.17.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.17.0/bin/yarn
    npm: 8.19.1 - ~/.nvm/versions/node/v16.17.0/bin/npm
  Browsers:
    Chrome: 105.0.5195.102
    Safari: 15.6.1

Used Package Manager

pnpm

Logs

Click to expand!

Node ESM

It should be Browser ESM.

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[Drafter500]

I have the same issue, except that even module path from package.json is ignored, and main is always used instead. This happens for executing a build (vite-build command) and when running a dev server, it picks the right one.

[segevfiner]

Ooofff the way Vite resolves entry points from package.json just seems all over the place and doesn't really match how Node or other bundlers work... Wish this could get some traction so I won't end up with so many weird cases of Vite trying to bundle Node code instead of browser. Heck, even the official @vue/devtools package is effected...

[bluwy]

This should be fixed by #11595

[segevfiner]

Well technically resolved. Not "not planned" but nevermind.