-
|
I was going to file an issue but realised that my understanding of the problem here is too vague; specifically I can't tell if the failure is Parcel's remit or something misconfigured elsewhere. After some dependency updates, I started getting these errors from Parcel builds: I'm currently using By rolling back individual dependencies, I figured out that the breaking change was:
But there are a few strange things going on:
So I'm confused about where the problem even lies: whether it's |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Parcel does not resolve package exports by default. See https://parceljs.org/features/dependency-resolution/#enabling-package-exports. To enable support for package exports, parcel users should add the following to their package.json: "@parcel/resolver-default": {
"packageExports": true
}This goes in the |
Beta Was this translation helpful? Give feedback.
Parcel does not resolve package exports by default. See https://parceljs.org/features/dependency-resolution/#enabling-package-exports. To enable support for package exports, parcel users should add the following to their package.json:
This goes in the
package.jsonof the application that uses parcel as bundler andzstddecas dependency, to configure parcel properly. There is nothing wrong withol,geotiffandzstddecin that regard.