`react-dom/server` cannot be resolved with `unstable_enablePackageExports` and condition `browser`

(As reported by @EvanBacon)

Metro cannot resolve react-dom/server with unable_enablePackageExports (and condition browser?), reporting:

warning: Attempted to import the module "/Users/evanbacon/Documents/GitHub/expo/node_modules/react-dom/server.browser.js" which is not listed in the "exports" of "/Users/evanbacon/Documents/GitHub/expo/node_modules/react-dom". Falling back to file-based resolution. Consider updating the call site or asking the package maintainer(s) to expose this API.

Conditions

  unstable_conditionNames: [ 'node', 'require' ],
  unstable_conditionsByPlatform: { web: [ 'browser' ] },

package.json

  "exports": {
    ".": "./index.js",
    "./client": "./client.js",
    "./server": {
      "deno": "./server.browser.js",
      "worker": "./server.browser.js",
      "browser": "./server.browser.js",
      "default": "./server.node.js"
    },
    "./server.browser": "./server.browser.js",
    "./server.node": "./server.node.js",
    "./profiling": "./profiling.js",
    "./test-utils": "./test-utils.js",
    "./package.json": "./package.json"
  },
  "browser": {
    "./server.js": "./server.browser.js"
  },

Start by reproducing the react-dom/server resolution with unstable_enablePackageExports and the shown browser condition. Inspect the package.json exports and browser mappings, including server.browser.js; done when Metro resolves the import without the fallback warning.