Ideally ethr-did-resolver should be rebuilt to only contain ESM code, but since we have no control over that and I do not want to fork them, we can inline the code directly during bundling, this is done by shifting ethr-did-resolver to dev deps (a microbundler behaviour).
Why
The ESM build of
ethr-did-resolver
seems to be mixing cjs, which will fail in esm only environments. Something like that https://github.com/decentralized-identity/ethr-did-resolver/issues/186.What
Ideally
ethr-did-resolver
should be rebuilt to only contain ESM code, but since we have no control over that and I do not want to fork them, we can inline the code directly during bundling, this is done by shiftingethr-did-resolver
to dev deps (a microbundler behaviour).