Open theblockstalk opened 1 month ago
did-resolver
did-jwt
did-jwt-vc
@tonomy/did-...
antelope-did-resolver
jest.config.ts
jsdom
jsdom-url
./test/test.setup.ts
yarn run cli
veramo.ts
did-jwk.ts
did-key.ts
API
utils
base64.ts
eslint
ExternalUser.getIssuer()
keyManager
Updated the resolver to use latest libraries and noble curves: https://github.com/Tonomy-Foundation/antelope-did-resolver/pull/15
TODO:
did-antelope-resolver@0.9.0
did-antelope-resolver
did-resolver
,did-jwt
anddid-jwt-vc
packages from DIF repo, instead of the outdated@tonomy/did-...
bundles https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/issues/336antelope-did-resolver
after it was upgraded https://github.com/Tonomy-Foundation/antelope-did-resolver/pull/15jest.config.ts
jsdom
andjsdom-url
package as not needed in latest jest. Added jsdom dependencies in./test/test.setup.ts
and removed jest custom environmentyarn run cli
also using ESM bundlesveramo.ts
and unit tests. to ensure we are ready for next tasks that depended on this upgrade https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/issues/337 to be ready for https://github.com/Tonomy-Foundation/Tonomy-ID/issues/758did-jwk.ts
and upgraded to usedid-key.ts
instead. this solves https://github.com/Tonomy-Foundation/Tonomy-ID-SDK/issues/316API
andutils
builds and conditional exportsbase64.ts
helper functions and unit testseslint
to use the new configuration file and conventions. Also removing and updating config dependency packagesExternalUser.getIssuer()
using the wrongkeyManager