[feature / bug?] allow non-"browser" dependancy priority when tree-shaking

[SilentCicero]

Currently, when using tree shaking, parcel will select dependancies "browser" specified build over the actual raw source, this leads to tree shaken builds which are not tree shaken!

Parcel should either select the raw source and not the "browser" builds of dependancies or allow me to remove that option.

I have tried hacking it myself and removing my dependancies "browser" property from their package JSON, but parcel doesn't seem to handle it all very well.

To recreate, npm init a package, create an index.js and index.html, install ethers module and import it into your build, than do a parcel build with tree shaking enabled. You will see it includes the entire minified browser specified ethers.min.js and no a tree shaken version of ethers.

[mischnic]

The problem is that the browser entry might have different behaviour than main or module and that there is no established browserModule field (not even with the new package.json#exports: #4155).

[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.