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
Uncaught (in promise) Error: Failed to resolve did:3:kjzl6cwe1jw14936apxr6lxhewn3srcpxjwjtu777mkfio7718ue8alc7pfr717?version-id=0#pn1iiYhhzD3kUev: invalidDid, TypeError: Cannot call a class as a function
at A.<anonymous> (index.ts:303)
at c (runtime.js:63)
The value of DID before the error is:
This issue does not occur in development. In development, the value of DID at the same location is:
A while ago I was trying to alter the system to have the capability to load components from arbitrary servers on the web to allow for a more robust plugin architecture.
I ejected the application and added Craco in an attempt to get it to generate standalone components.
I never got it to work and seem to have broken Webpack in the process.
Bug Description
When the button is clicked on https://dysbulic.github.io/xml-to-ipld/#/ceramic the application crashes with the following error:
The value of
DID
before the error is:This issue does not occur in development. In development, the value of
DID
at the same location is:The code being run is:
Then in
@ceramicnetwork/http-client
:It dies calling
new DID()
.To Reproduce
git clone https://github.com/dysbulic/xml-to-ipld.git
cd xml-to-ipld && yarn && yarn start
Expected Behavior
I would like the behavior in production to be the same as development.
Ceramic Versions
@ceramicnetwork/3id-did-resolver@^1.1.1
@ceramicnetwork/common@^0.17.0
@ceramicnetwork/docid@^0.5.1
@ceramicnetwork/doctype-caip10-link@^0.13.4
@ceramicnetwork/doctype-tile@^0.14.1
@ceramicnetwork/http-client@^0.10.1
@ceramicstudio/idx@^0.7.0
@ceramicstudio/idx-tools@0.9.0
Machine, OS, Browser Information
Linux fenrir 5.8.0-48-generic #54~20.04.1-Ubuntu SMP Sat Mar 20 13:40:25 UTC 2021 x86_64 GNU/Linux
accounts[0]
is not defined.window.ethereum
is not defined.Additional Information
It looks to me like the minimizer made a mistake, but that just seems so unlikely.
The text was updated successfully, but these errors were encountered: