[Bug?]: Handling of package.json#exports is not working correctly with intermediate wildcard.

[gpickell]

Self-service

• I'd be willing to implement a fix

Describe the bug

When using yarn with pnp linking, the handling of the * in a package.json#exports has a compatibility issue. Mainly, if the * appears in the middle, it fails, but this is supported with node out-of-the-box.

package.json:

  ...

  "exports": {
    "./*/index": "./src/*.mjs", // not honored when linking pnp-style but works otherwise
    "./*": "./src/*.mjs" // works always
  }

  ...

To reproduce

See: https://github.com/gpickell/yarn-bug-exports-handling

yarn
yarn test # works
# remove nodeLinker line from .yarnrc.yml
yarn
yarn test # fails

Environment

System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
  Binaries:
    Node: 16.16.0 - ~\AppData\Local\Temp\xfs-a40a0340\node.CMD
    Yarn: 3.2.3 - ~\AppData\Local\Temp\xfs-a40a0340\yarn.CMD
    npm: 8.11.0 - ~\AppData\Local\nvs\node\16.16.0\x64\npm.CMD

Additional context

No response

[arcanis]

The exports support is provided by https://github.com/lukeed/resolve.exports, a bug should be open there

[gpickell]

I am issuing a pull request to resolve.exports --- more eyes would be appreciated.
See: lukeed/resolve.exports#21

[gpickell]

I think the resolve.exports project might be a little on the "inactive side".

[merceyz]

Indeed, I have a branch that fixes the issue but haven't had the time to complete it yet.

[gpickell]

I believe resolve.exports project has been updated to fix this issue. The pull request is no longer relevant.