Error while installing blockstack-cli as part of the Blockstack test net getting started guide

Core Blockchain Command Line (CLI)
#1

I followed these steps as per the getting started guide https://testnet.blockstack.org/

git clone https://github.com/blockstack/blockstack.js
cd blockstack.js
git checkout -b feature/stack-transactions
npm install
npm run build
npm link 
cd ..
git clone https://github.com/jcnelson/cli-blockstack
cd cli-blockstack
npm link blockstack
npm install

The last command i.e. npm install fails with the following error:

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!     /root/.npm/_logs/2018-08-24T06_53_23_011Z-debug.log

So I tried working around this with:
npm install ../blockstack.js
followed by
npm install
This seems to go through successfully.
But after this, the blockstack-cli is not available in PATH, like how it appears to be in the video https://www.youtube.com/watch?v=hDuYWeDmm8o
Am I missing something here ?

#2

You need to run sudo npm install -g or sudo npm link to install the blockstack-cli globally.

#3
  1. git clone https://github.com/blockstack/blockstack.js
  2. cd blockstack.js/
  3. git checkout -b feature/stack-transactions
  4. npm install -g
  5. npm link
  6. npm run build
  7. cd …
  8. git clone https://github.com/jcnelson/cli-blockstack
  9. cd cli-blockstack
  10. npm link blockstack
    11.npm install( that have a problem)

When I execute step 11 that have problem:

npm ERR! path /usr/local/lib/node_modules/blockstack-cli/lib/index.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod ‘/usr/local/lib/node_modules/blockstack-cli/lib/index.js’
npm ERR! enoent This is related to npm not being able to find a file.