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
Guys, in your packages, for example in @v4-sdk, you import a lot of stuff from 'ethers/lib/utils', which is compatible with ethers v5 but not with v6.
But, since it's not presented in any of package.json files, your imports are referencing workspace's ethers version, which is in a lot of times v6.
So, this leads to build crashes with Package subpath './lib/utils' is not defined by "exports" error across the globe.
For the ones who's seeing it, this resolves the issue.
Guys, in your packages, for example in @v4-sdk, you import a lot of stuff from 'ethers/lib/utils', which is compatible with ethers v5 but not with v6.
But, since it's not presented in any of package.json files, your imports are referencing workspace's ethers version, which is in a lot of times v6.
So, this leads to build crashes with
Package subpath './lib/utils' is not defined by "exports"
error across the globe.For the ones who's seeing it, this resolves the issue.
The text was updated successfully, but these errors were encountered: