Open ChristopherA opened 4 years ago
dfriedenberger
commented
4 years ago I can reproduce the error on windows 10 with mingw
npm i -g @github-did/cli
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm ERR! code 1
npm ERR! Command failed: git checkout initial
npm ERR! error: pathspec 'initial' did not match any file(s) known to git
npm ERR!according to #68 tested with node10, but also is not working
C:\Users\DirkFriedenberger>docker run -it node:10 bash
root@e85ca29aff3e:/# npm i -g @github-did/cli
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm ERR! code 1
npm ERR! Command failed: git checkout initial
npm ERR! error: pathspec 'initial' did not match any file(s) known to git.
npm ERR!
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-09-17T20_57_01_076Z-debug.log
root@e85ca29aff3e:/#Library "did-method-key" in version 0.0.2 produces this error, version 0.7.0 works!
root@396bb1ab9399:~# npm install did-method-key@0.2.0
npm ERR! code 1
npm ERR! Command failed: git checkout initial
npm ERR! error: pathspec 'initial' did not match any file(s) known to git.
npm ERR!Add the end I could create https://github.com/dfriedenberger/ghdid with following workaround, which also can be a solution for the bug.
git clone https://github.com/decentralized-identity/github-did.git
cd github-did/packages/cd lib/- "did-method-key": "^0.2.0",
+ "did-method-key": "^0.7.0",await in src/v2/func/createDIDDoc.js:95 (without await tests (npm run test) will fail)- const didDoc = keyToDidDoc(edKey);
+ const didDoc = await keyToDidDoc(edKey);npm installcd ../cli- "@github-did/lib": "^0.0.5",
+ "@github-did/lib": "file:../lib",npm run ghdid init init "my-password" https://github.com/USERNAME/ghdid
smallyunet
commented
3 years ago I had the same problem on linux, have any simple methods fixed it?
npm i @github-did/lib --save
npm WARN deprecated har-validator@5.1.5: this
npm ERR! code 1
npm ERR! Command failed: git checkout initial
npm ERR! error: pathspec 'initial' did not match any file(s) known to git.
npm ERR! 
studyzy
commented
3 years ago debug.log:
0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/usr/local/bin/node', 1 verbose cli '/usr/local/bin/npm', 1 verbose cli 'i', 1 verbose cli '-g', 1 verbose cli '@github-did/cli' 1 verbose cli ] 2 info using npm@6.14.9 3 info using node@v14.15.2 4 verbose npm-session 05c2aef0a52c4614 5 silly install loadCurrentTree 6 silly install readGlobalPackageData 7 http fetch GET 304 https://registry.npmjs.org/@github-did%2fcli 1593ms (from cache) 8 silly pacote tag manifest for @github-did/cli@latest fetched in 1616ms 9 timing stage:loadCurrentTree Completed in 1718ms 10 silly install loadIdealTree 11 silly install cloneCurrentTreeToIdealTree 12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms 13 silly install loadShrinkwrap 14 timing stage:loadIdealTree:loadShrinkwrap Completed in 3ms 15 silly install loadAllDepsIntoIdealTree 16 silly resolveWithNewModule @github-did/cli@0.0.5 checking installable status 17 http fetch GET 200 https://registry.npmjs.org/fs-extra 62ms (from cache) 18 silly pacote range manifest for fs-extra@^7.0.1 fetched in 67ms 19 silly resolveWithNewModule fs-extra@7.0.1 checking installable status 20 http fetch GET 304 https://registry.npmjs.org/@github-did%2flib 671ms (from cache) 21 silly pacote range manifest for @github-did/lib@^0.0.5 fetched in 676ms 22 silly resolveWithNewModule @github-did/lib@0.0.5 checking installable status 23 http fetch GET 304 https://registry.npmjs.org/node-fetch 1017ms (from cache) 24 http fetch GET 304 https://registry.npmjs.org/uuid 1018ms (from cache) 25 silly pacote range manifest for node-fetch@^2.3.0 fetched in 1026ms 26 silly resolveWithNewModule node-fetch@2.6.1 checking installable status 27 http fetch GET 304 https://registry.npmjs.org/winston 1017ms (from cache) 28 http fetch GET 304 https://registry.npmjs.org/vorpal 1025ms (from cache) 29 http fetch GET 304 https://registry.npmjs.org/shelljs 1031ms (from cache) 30 silly pacote range manifest for uuid@^3.3.2 fetched in 1032ms 31 silly resolveWithNewModule uuid@3.4.0 checking installable status 32 silly pacote range manifest for winston@^3.1.0 fetched in 1036ms 33 silly resolveWithNewModule winston@3.3.3 checking installable status 34 silly pacote range manifest for shelljs@^0.8.3 fetched in 1043ms 35 silly resolveWithNewModule shelljs@0.8.4 checking installable status 36 silly pacote range manifest for vorpal@^1.12.0 fetched in 1043ms 37 silly resolveWithNewModule vorpal@1.12.0 checking installable status 38 http fetch GET 304 https://registry.npmjs.org/openpgp 1064ms (from cache) 39 silly pacote range manifest for openpgp@^4.4.3 fetched in 1076ms 40 silly resolveWithNewModule openpgp@4.10.9 checking installable status 41 http fetch GET 304 https://registry.npmjs.org/@transmute%2fopenpgpsignature2019 1402ms (from cache) 42 silly pacote range manifest for @transmute/openpgpsignature2019@^0.1.1 fetched in 1405ms 43 silly resolveWithNewModule @transmute/openpgpsignature2019@0.1.1 checking installable status 44 http fetch GET 304 https://registry.npmjs.org/jsonwebtoken 313ms (from cache) 45 http fetch GET 304 https://registry.npmjs.org/moment 314ms (from cache) 46 silly pacote range manifest for jsonwebtoken@^8.5.0 fetched in 318ms 47 silly resolveWithNewModule jsonwebtoken@8.5.1 checking installable status 48 silly pacote range manifest for moment@^2.24.0 fetched in 319ms 49 silly resolveWithNewModule moment@2.29.1 checking installable status 50 http fetch GET 304 https://registry.npmjs.org/crypto-ld 417ms (from cache) 51 http fetch GET 304 https://registry.npmjs.org/jsonld-signatures 417ms (from cache) 52 silly pacote range manifest for crypto-ld@^3.7.0 fetched in 423ms 53 silly resolveWithNewModule crypto-ld@3.9.0 checking installable status 54 silly pacote range manifest for jsonld-signatures@^4.4.0 fetched in 422ms 55 silly resolveWithNewModule jsonld-signatures@4.6.0 checking installable status 56 http fetch GET 304 https://registry.npmjs.org/did-method-key 439ms (from cache) 57 silly pacote range manifest for did-method-key@^0.2.0 fetched in 447ms 58 silly resolveWithNewModule did-method-key@0.2.0 checking installable status 59 http fetch GET 304 https://registry.npmjs.org/@transmute%2frsasignature2017 678ms (from cache) 60 silly pacote range manifest for @transmute/rsasignature2017@^0.1.0 fetched in 681ms 61 silly resolveWithNewModule @transmute/rsasignature2017@0.1.0 checking installable status 62 http fetch GET 304 https://registry.npmjs.org/@transmute%2fdid-wallet 707ms (from cache) 63 silly pacote version manifest for @transmute/did-wallet@0.0.0-5 fetched in 713ms 64 silly resolveWithNewModule @transmute/did-wallet@0.0.0-5 checking installable status 65 http fetch GET 304 https://registry.npmjs.org/jsonschema 289ms (from cache) 66 silly pacote range manifest for jsonschema@^1.2.4 fetched in 297ms 67 silly resolveWithNewModule jsonschema@1.4.0 checking installable status 68 http fetch GET 304 https://registry.npmjs.org/base64url 308ms (from cache) 69 silly pacote range manifest for base64url@^3.0.1 fetched in 311ms 70 silly resolveWithNewModule base64url@3.0.1 checking installable status 71 http fetch GET 304 https://registry.npmjs.org/lodash 312ms (from cache) 72 silly pacote range manifest for lodash@^4.17.11 fetched in 314ms 73 silly resolveWithNewModule lodash@4.17.20 checking installable status 74 http fetch GET 304 https://registry.npmjs.org/jsonld 286ms (from cache) 75 silly pacote range manifest for jsonld@^1.4.0 fetched in 293ms 76 silly resolveWithNewModule jsonld@1.8.1 checking installable status 77 http fetch GET 200 https://registry.npmjs.org/semver 16ms (from cache) 78 silly pacote range manifest for semver@^5.6.0 fetched in 20ms 79 silly resolveWithNewModule semver@5.7.1 checking installable status 80 http fetch GET 304 https://registry.npmjs.org/xmldom 290ms (from cache) 81 silly pacote version manifest for xmldom@0.1.19 fetched in 300ms 82 silly resolveWithNewModule xmldom@0.1.19 checking installable status 83 http fetch GET 304 https://registry.npmjs.org/canonicalize 321ms (from cache) 84 http fetch GET 304 https://registry.npmjs.org/rdf-canonize 322ms (from cache) 85 http fetch GET 304 https://registry.npmjs.org/request 323ms (from cache) 86 silly pacote range manifest for canonicalize@^1.0.1 fetched in 328ms 87 silly resolveWithNewModule canonicalize@1.0.5 checking installable status 88 silly pacote range manifest for rdf-canonize@^1.0.2 fetched in 330ms 89 silly resolveWithNewModule rdf-canonize@1.2.0 checking installable status 90 silly pacote range manifest for request@^2.88.0 fetched in 330ms 91 warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 92 silly resolveWithNewModule request@2.88.2 checking installable status 93 silly pacote range manifest for semver@^6.3.0 fetched in 2ms 94 silly resolveWithNewModule semver@6.3.0 checking installable status 95 http fetch GET 304 https://registry.npmjs.org/node-forge 370ms (from cache) 96 silly pacote range manifest for node-forge@^0.10.0 fetched in 377ms 97 silly resolveWithNewModule node-forge@0.10.0 checking installable status 98 http fetch GET 304 https://registry.npmjs.org/aws4 342ms (from cache) 99 http fetch GET 304 https://registry.npmjs.org/caseless 342ms (from cache) 100 http fetch GET 304 https://registry.npmjs.org/aws-sign2 345ms (from cache) 101 http fetch GET 304 https://registry.npmjs.org/extend 345ms (from cache) 102 silly pacote range manifest for aws4@^1.8.0 fetched in 349ms 103 silly resolveWithNewModule aws4@1.11.0 checking installable status 104 silly pacote range manifest for caseless@~0.12.0 fetched in 349ms 105 silly resolveWithNewModule caseless@0.12.0 checking installable status 106 http fetch GET 304 https://registry.npmjs.org/http-signature 347ms (from cache) 107 http fetch GET 304 https://registry.npmjs.org/forever-agent 355ms (from cache) 108 silly pacote range manifest for aws-sign2@~0.7.0 fetched in 358ms 109 silly resolveWithNewModule aws-sign2@0.7.0 checking installable status 110 http fetch GET 304 https://registry.npmjs.org/combined-stream 360ms (from cache) 111 silly pacote range manifest for extend@~3.0.2 fetched in 360ms 112 silly resolveWithNewModule extend@3.0.2 checking installable status 113 http fetch GET 304 https://registry.npmjs.org/form-data 362ms (from cache) 114 silly pacote range manifest for http-signature@~1.2.0 fetched in 366ms 115 silly resolveWithNewModule http-signature@1.2.0 checking installable status 116 silly pacote range manifest for forever-agent@~0.6.1 fetched in 373ms 117 silly resolveWithNewModule forever-agent@0.6.1 checking installable status 118 silly pacote range manifest for combined-stream@~1.0.6 fetched in 377ms 119 silly resolveWithNewModule combined-stream@1.0.8 checking installable status 120 silly pacote range manifest for form-data@~2.3.2 fetched in 380ms 121 silly resolveWithNewModule form-data@2.3.3 checking installable status 122 http fetch GET 200 https://registry.npmjs.org/safe-buffer 14ms (from cache) 123 silly pacote range manifest for safe-buffer@^5.1.2 fetched in 16ms 124 silly resolveWithNewModule safe-buffer@5.2.1 checking installable status 125 http fetch GET 304 https://registry.npmjs.org/mime-types 335ms (from cache) 126 http fetch GET 304 https://registry.npmjs.org/isstream 343ms (from cache) 127 http fetch GET 304 https://registry.npmjs.org/performance-now 322ms (from cache) 128 http fetch GET 304 https://registry.npmjs.org/json-stringify-safe 344ms (from cache) 129 http fetch GET 304 https://registry.npmjs.org/oauth-sign 337ms (from cache) 130 silly pacote range manifest for mime-types@~2.1.19 fetched in 344ms 131 silly resolveWithNewModule mime-types@2.1.27 checking installable status 132 silly pacote range manifest for json-stringify-safe@~5.0.1 fetched in 352ms 133 silly resolveWithNewModule json-stringify-safe@5.0.1 checking installable status 134 silly pacote range manifest for isstream@~0.1.2 fetched in 355ms 135 silly resolveWithNewModule isstream@0.1.2 checking installable status 136 silly pacote range manifest for performance-now@^2.1.0 fetched in 334ms 137 silly resolveWithNewModule performance-now@2.1.0 checking installable status 138 http fetch GET 304 https://registry.npmjs.org/qs 332ms (from cache) 139 silly pacote range manifest for oauth-sign@~0.9.0 fetched in 347ms 140 silly resolveWithNewModule oauth-sign@0.9.0 checking installable status 141 http fetch GET 304 https://registry.npmjs.org/tough-cookie 327ms (from cache) 142 http fetch GET 304 https://registry.npmjs.org/tunnel-agent 315ms (from cache) 143 silly pacote range manifest for qs@~6.5.2 fetched in 338ms 144 silly resolveWithNewModule qs@6.5.2 checking installable status 145 silly pacote range manifest for tough-cookie@~2.5.0 fetched in 331ms 146 silly resolveWithNewModule tough-cookie@2.5.0 checking installable status 147 silly pacote range manifest for tunnel-agent@^0.6.0 fetched in 320ms 148 silly resolveWithNewModule tunnel-agent@0.6.0 checking installable status 149 http fetch GET 304 https://registry.npmjs.org/har-validator 797ms (from cache) 150 silly pacote range manifest for har-validator@~5.1.3 fetched in 799ms 151 warn deprecated har-validator@5.1.5: this library is no longer supported 152 silly resolveWithNewModule har-validator@5.1.5 checking installable status 153 http fetch GET 304 https://registry.npmjs.org/is-typedarray 837ms (from cache) 154 silly pacote range manifest for is-typedarray@~1.0.0 fetched in 839ms 155 silly resolveWithNewModule is-typedarray@1.0.0 checking installable status 156 http fetch GET 304 https://registry.npmjs.org/delayed-stream 287ms (from cache) 157 silly pacote range manifest for delayed-stream@~1.0.0 fetched in 289ms 158 silly resolveWithNewModule delayed-stream@1.0.0 checking installable status 159 http fetch GET 304 https://registry.npmjs.org/asynckit 317ms (from cache) 160 silly pacote range manifest for asynckit@^0.4.0 fetched in 319ms 161 silly resolveWithNewModule asynckit@0.4.0 checking installable status 162 http fetch GET 304 https://registry.npmjs.org/mime-db 292ms (from cache) 163 silly pacote version manifest for mime-db@1.44.0 fetched in 296ms 164 silly resolveWithNewModule mime-db@1.44.0 checking installable status 165 http fetch GET 304 https://registry.npmjs.org/har-schema 287ms (from cache) 166 silly pacote range manifest for har-schema@^2.0.0 fetched in 291ms 167 silly resolveWithNewModule har-schema@2.0.0 checking installable status 168 http fetch GET 304 https://registry.npmjs.org/ajv 1496ms (from cache) 169 silly pacote range manifest for ajv@^6.12.3 fetched in 1506ms 170 silly resolveWithNewModule ajv@6.12.6 checking installable status 171 http fetch GET 304 https://registry.npmjs.org/json-schema-traverse 283ms (from cache) 172 silly pacote range manifest for json-schema-traverse@^0.4.1 fetched in 288ms 173 silly resolveWithNewModule json-schema-traverse@0.4.1 checking installable status 174 http fetch GET 304 https://registry.npmjs.org/fast-deep-equal 294ms (from cache) 175 silly pacote range manifest for fast-deep-equal@^3.1.1 fetched in 297ms 176 silly resolveWithNewModule fast-deep-equal@3.1.3 checking installable status 177 http fetch GET 304 https://registry.npmjs.org/uri-js 300ms (from cache) 178 http fetch GET 304 https://registry.npmjs.org/fast-json-stable-stringify 304ms (from cache) 179 silly pacote range manifest for uri-js@^4.2.2 fetched in 304ms 180 silly resolveWithNewModule uri-js@4.4.0 checking installable status 181 silly pacote range manifest for fast-json-stable-stringify@^2.0.0 fetched in 307ms 182 silly resolveWithNewModule fast-json-stable-stringify@2.1.0 checking installable status 183 http fetch GET 304 https://registry.npmjs.org/punycode 270ms (from cache) 184 silly pacote range manifest for punycode@^2.1.0 fetched in 273ms 185 silly resolveWithNewModule punycode@2.1.1 checking installable status 186 http fetch GET 304 https://registry.npmjs.org/assert-plus 292ms (from cache) 187 http fetch GET 304 https://registry.npmjs.org/sshpk 292ms (from cache) 188 silly pacote range manifest for assert-plus@^1.0.0 fetched in 295ms 189 silly resolveWithNewModule assert-plus@1.0.0 checking installable status 190 silly pacote range manifest for sshpk@^1.7.0 fetched in 296ms 191 silly resolveWithNewModule sshpk@1.16.1 checking installable status 192 http fetch GET 304 https://registry.npmjs.org/jsprim 297ms (from cache) 193 silly pacote range manifest for jsprim@^1.2.2 fetched in 299ms 194 silly resolveWithNewModule jsprim@1.4.1 checking installable status 195 http fetch GET 304 https://registry.npmjs.org/verror 283ms (from cache) 196 silly pacote version manifest for verror@1.10.0 fetched in 286ms 197 silly resolveWithNewModule verror@1.10.0 checking installable status 198 http fetch GET 304 https://registry.npmjs.org/json-schema 289ms (from cache) 199 silly pacote version manifest for json-schema@0.2.3 fetched in 290ms 200 silly resolveWithNewModule json-schema@0.2.3 checking installable status 201 http fetch GET 304 https://registry.npmjs.org/extsprintf 291ms (from cache) 202 silly pacote version manifest for extsprintf@1.3.0 fetched in 294ms 203 silly resolveWithNewModule extsprintf@1.3.0 checking installable status 204 http fetch GET 304 https://registry.npmjs.org/core-util-is 271ms (from cache) 205 silly pacote version manifest for core-util-is@1.0.2 fetched in 273ms 206 silly resolveWithNewModule core-util-is@1.0.2 checking installable status 207 http fetch GET 304 https://registry.npmjs.org/dashdash 300ms (from cache) 208 http fetch GET 304 https://registry.npmjs.org/bcrypt-pbkdf 300ms (from cache) 209 silly pacote range manifest for dashdash@^1.12.0 fetched in 306ms 210 silly resolveWithNewModule dashdash@1.14.1 checking installable status 211 silly pacote range manifest for bcrypt-pbkdf@^1.0.0 fetched in 305ms 212 silly resolveWithNewModule bcrypt-pbkdf@1.0.2 checking installable status 213 http fetch GET 304 https://registry.npmjs.org/getpass 308ms (from cache) 214 silly pacote range manifest for getpass@^0.1.1 fetched in 313ms 215 silly resolveWithNewModule getpass@0.1.7 checking installable status 216 http fetch GET 304 https://registry.npmjs.org/ecc-jsbn 313ms (from cache) 217 http fetch GET 304 https://registry.npmjs.org/tweetnacl 314ms (from cache) 218 http fetch GET 304 https://registry.npmjs.org/jsbn 316ms (from cache) 219 http fetch GET 304 https://registry.npmjs.org/asn1 321ms (from cache) 220 http fetch GET 304 https://registry.npmjs.org/safer-buffer 319ms (from cache) 221 silly pacote range manifest for asn1@~0.2.3 fetched in 339ms 222 silly resolveWithNewModule asn1@0.2.4 checking installable status 223 silly pacote range manifest for tweetnacl@~0.14.0 fetched in 338ms 224 silly resolveWithNewModule tweetnacl@0.14.5 checking installable status 225 silly pacote range manifest for jsbn@~0.1.0 fetched in 339ms 226 silly resolveWithNewModule jsbn@0.1.1 checking installable status 227 silly pacote range manifest for ecc-jsbn@~0.1.1 fetched in 338ms 228 silly resolveWithNewModule ecc-jsbn@0.1.2 checking installable status 229 silly pacote range manifest for safer-buffer@^2.0.2 fetched in 341ms 230 silly resolveWithNewModule safer-buffer@2.1.2 checking installable status 231 http fetch GET 304 https://registry.npmjs.org/psl 371ms (from cache) 232 silly pacote range manifest for psl@^1.1.28 fetched in 375ms 233 silly resolveWithNewModule psl@1.8.0 checking installable status 234 http fetch GET 304 https://registry.npmjs.org/asn1.js 385ms (from cache) 235 silly pacote range manifest for asn1.js@^5.0.0 fetched in 387ms 236 silly resolveWithNewModule asn1.js@5.4.1 checking installable status 237 http fetch GET 304 https://registry.npmjs.org/node-localstorage 388ms (from cache) 238 silly pacote range manifest for node-localstorage@~1.3.0 fetched in 390ms 239 silly resolveWithNewModule node-localstorage@1.3.1 checking installable status 240 http fetch GET 304 https://registry.npmjs.org/bn.js 269ms (from cache) 241 silly pacote range manifest for bn.js@^4.0.0 fetched in 272ms 242 silly resolveWithNewModule bn.js@4.11.9 checking installable status 243 http fetch GET 304 https://registry.npmjs.org/inherits 292ms (from cache) 244 silly pacote range manifest for inherits@^2.0.1 fetched in 294ms 245 silly resolveWithNewModule inherits@2.0.4 checking installable status 246 http fetch GET 304 https://registry.npmjs.org/minimalistic-assert 819ms (from cache) 247 silly pacote range manifest for minimalistic-assert@^1.0.0 fetched in 821ms 248 silly resolveWithNewModule minimalistic-assert@1.0.1 checking installable status 249 http fetch GET 304 https://registry.npmjs.org/write-file-atomic 281ms (from cache) 250 silly pacote range manifest for write-file-atomic@^1.1.4 fetched in 283ms 251 silly resolveWithNewModule write-file-atomic@1.3.4 checking installable status 252 http fetch GET 304 https://registry.npmjs.org/imurmurhash 255ms (from cache) 253 silly pacote range manifest for imurmurhash@^0.1.4 fetched in 257ms 254 silly resolveWithNewModule imurmurhash@0.1.4 checking installable status 255 http fetch GET 304 https://registry.npmjs.org/slide 286ms (from cache) 256 http fetch GET 304 https://registry.npmjs.org/graceful-fs 288ms (from cache) 257 silly pacote range manifest for slide@^1.1.5 fetched in 289ms 258 silly resolveWithNewModule slide@1.1.6 checking installable status 259 silly pacote range manifest for graceful-fs@^4.1.11 fetched in 290ms 260 silly resolveWithNewModule graceful-fs@4.2.4 checking installable status 261 http fetch GET 304 https://registry.npmjs.org/generate-rsa-keypair 399ms (from cache) 262 silly pacote range manifest for generate-rsa-keypair@^0.1.2 fetched in 402ms 263 silly resolveWithNewModule generate-rsa-keypair@0.1.2 checking installable status 264 http fetch GET 304 https://registry.npmjs.org/nan 400ms (from cache) 265 silly pacote range manifest for nan@^2.10.0 fetched in 403ms 266 silly resolveWithNewModule nan@2.14.2 checking installable status 267 silly pacote range manifest for semver@^6.2.0 fetched in 3ms 268 silly resolveWithNewModule semver@6.3.0 checking installable status 269 http fetch GET 304 https://registry.npmjs.org/bs58 286ms (from cache) 270 silly pacote range manifest for bs58@^4.0.1 fetched in 288ms 271 silly resolveWithNewModule bs58@4.0.1 checking installable status 272 http fetch GET 304 https://registry.npmjs.org/base64url-universal 387ms (from cache) 273 silly pacote range manifest for base64url-universal@^1.0.1 fetched in 389ms 274 silly resolveWithNewModule base64url-universal@1.1.0 checking installable status 275 http fetch GET 304 https://registry.npmjs.org/sodium-native 947ms (from cache) 276 silly pacote range manifest for sodium-native@^3.2.0 fetched in 950ms 277 silly resolveWithNewModule sodium-native@3.2.0 checking installable status 278 http fetch GET 304 https://registry.npmjs.org/base-x 291ms (from cache) 279 silly pacote range manifest for base-x@^3.0.2 fetched in 293ms 280 silly resolveWithNewModule base-x@3.0.8 checking installable status 281 http fetch GET 304 https://registry.npmjs.org/node-gyp-build 273ms (from cache) 282 silly pacote range manifest for node-gyp-build@^4.2.0 fetched in 275ms 283 silly resolveWithNewModule node-gyp-build@4.2.3 checking installable status 284 http fetch GET 304 https://registry.npmjs.org/ini 329ms (from cache) 285 silly pacote range manifest for ini@^1.3.5 fetched in 333ms 286 silly resolveWithNewModule ini@1.3.8 checking installable status 287 silly fetchPackageMetaData error for x25519-key-pair@github:digitalbazaar/x25519-key-pair#initial Command failed: git checkout initial 287 silly fetchPackageMetaData error: pathspec 'initial' did not match any file(s) known to git 288 timing stage:rollbackFailedOptional Completed in 1ms 289 timing stage:runTopLevelLifecycles Completed in 18267ms 290 verbose stack Error: Command failed: git checkout initial 290 verbose stack error: pathspec 'initial' did not match any file(s) known to git 290 verbose stack 290 verbose stack at ChildProcess.exithandler (child_process.js:308:12) 290 verbose stack at ChildProcess.emit (events.js:315:20) 290 verbose stack at maybeClose (internal/child_process.js:1048:16) 290 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5) 291 verbose cwd /Users/studyzy 292 verbose Darwin 19.6.0 293 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "i" "-g" "@github-did/cli" 294 verbose node v14.15.2 295 verbose npm v6.14.9 296 error code 1 297 error Command failed: git checkout initial 297 error error: pathspec 'initial' did not match any file(s) known to git 298 verbose exit [ 1, true ]
I wanted to try out github-did on MacOS, and I generally don't use npm or javascript.
I am encountering problems following the initial instructions on the website at https://github-did.com:
Like I've found with some other projects like this, my development system system is not npm/javascript centric, so there is probably some unlisted dependency that most npm/javascript developers have but I do not.