You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Over in the main berry repo, support for the package.jsonexports field was added in this PR, here in the code. However, this code is not called by the plugin, which calls findPackageLocator directly, here:
This breaks my monorepo setup, which uses an exports field in a package like this:
"exports": {
"./*": "./build/*"
},
I'm not familiar with the intricacies of the PnP api, but would it be possible to call resolveRequest instead, which (if I'm reading the source correctly) would call applyNodeExportsResolution eventually, instead of findPackageLocator which does not?
The text was updated successfully, but these errors were encountered:
Over in the main berry repo, support for the
package.json
exports
field was added in this PR, here in the code. However, this code is not called by the plugin, which callsfindPackageLocator
directly, here:pnp-webpack-plugin/index.js
Line 17 in 91aa446
This breaks my monorepo setup, which uses an
exports
field in a package like this:I'm not familiar with the intricacies of the PnP api, but would it be possible to call
resolveRequest
instead, which (if I'm reading the source correctly) would callapplyNodeExportsResolution
eventually, instead offindPackageLocator
which does not?The text was updated successfully, but these errors were encountered: