Exports map resolver config within monorepos

[achingbrain]

🐛 bug report

I see that from 2.9.x Parcel supports the package.json exports map with a small config change, great!

I was adding an example using Parcel to helia-examples - it's a monorepo consisting of lots of different projects. They all pertain to Helia - a project that uses only an exports map.

Parcel is executed from the /examples/helia-parcel directory so I added the @parcel/resolver-default config key to the Parcel example's package.json file but it didn't work.

It only started working when I added it to the root package.json which doesn't seem right.

Also, possibly related is that the .parcel-cache directory appears in the root of the monorepo instead of in /examples/helia-parcel where the command is executed.

🎛 Configuration (.babelrc, package.json, cli command)

No config other than:

{
  "@parcel/resolver-default": {
    "packageExports": true
  }
}

CLI:

parcel build src/index.html
parcel serve src/index.html --open -p 8888

🤔 Expected Behavior

Parcel should use the config keys in the local package.json and not require them to be elsewhere.

😯 Current Behavior

Parcel needs it in the monorepo parent package.json.

💁 Possible Solution

🤷

🔦 Context

The example needs extra configuration in an unrelated location, which is confusing for users.

💻 Code Sample

See: https://github.com/ipfs-examples/helia-examples

🌍 Your Environment

Software	Version(s)
Parcel	2.9.1
Node	18.16.0
npm/Yarn	npm 9.6.7
Operating System	Mac OS X

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.