Hi @Jude
I just tried using the updated instructions at https://github.com/jcnelson/cli-blockstack.
Note: Using sudo gave write access errors. I therefore used the following
$ git clone https://github.com/blockstack/blockstack.js
$ cd blockstack.js
$ git checkout feature/stacks-transactions # or feature/stacks-transactions-authResponse-1.3
$ npm install
$ npm link
This properly compiles the 19.0.0 version, and links it in /usr/local/lib/node_modules
Then, running
$ git clone https://github.com/jcnelson/cli-blockstack
$ cd cli-blockstack
$ npm install
$ npm link blockstack
Properly compiles cli-blockstack, and properly links blockstack to version 19.0.0 in local node_modules folder.
However, after running npm run build
, the blockstack version in the local node_modules folder is back to “18.0.4”
Finally running npm install
compiles, but with blockstack 18.0.4, and I still get the error
Ya-L-2:cli-blockstack yalb$ blockstack-cli balance SPZY1V53Z4TVRHHW9Z7SFG8CZNRAG7BD8WJ6SXD0
TypeError: network.getAccountTokens is not a function
at /Users/yalb/Projects/CurrentProjects/Blockchain/Blockstack/mybs/cli-blockstack/lib/cli.js:2128:20
at
at process._tickCallback (internal/process/next_tick.js:189:7)
at Function.Module.runMain (module.js:696:11)
at startup (bootstrap_node.js:204:16)
at bootstrap_node.js:625:3
network.getAccountTokens is not a function
I also tried to change the package.json in cli-blockstack so it requires blockstack version 19.0.0 (after executing ‘npm link blockstack’, so the local node_modules folder has blockstack 19.0.0);
Surprisingly, running ‘npm install’ now tells me that blockstack 19.0.0 cannot be found
Ya-L-2:cli-blockstack yalb$ npm install
npm ERR! code ETARGET
npm ERR! notarget No matching version found for blockstack@^19.0.0
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn’t exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of ‘blockstack-cli’
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/yalb/.npm/_logs/2018-10-01T07_42_16_216Z-debug.log
Node version: 8.12.0
npm version: 6.4.1