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
In a project with complex dependency tree it can happen that there are 2 or more versions of did-resolver in use.
The class Resolver has a private registry member, which leads to broken builds when it is imported from different versions of the library.
Argument of type '{ [x: string]: DIDResolver | DIDResolver; }' is not assignable to parameter of type 'ResolverRegistry'.
'string' index signatures are incompatible.
Type 'DIDResolver | DIDResolver' is not assignable to type 'DIDResolver'.
Type 'import("..../node_modules/did-resolver/lib/resolver").DIDResolver' is not assignable to type 'import("..../node_modules/did-resolver/lib/resolver").DIDResolver'.
Types of parameters 'resolver' and 'resolver' are incompatible.
Type 'import("..../node_modules/did-resolver/lib/resolver").Resolver' is not assignable to type 'import("..../node_modules/did-resolver/lib/resolver").Resolver'.
Types have separate declarations of a private property 'registry'.
I believe this could be fixed by avoiding the use of class Resolver as a type in other definitions.
The text was updated successfully, but these errors were encountered:
In a project with complex dependency tree it can happen that there are 2 or more versions of
did-resolver
in use.The class
Resolver
has a privateregistry
member, which leads to broken builds when it is imported from different versions of the library.I believe this could be fixed by avoiding the use of
class Resolver
as a type in other definitions.The text was updated successfully, but these errors were encountered: