npm ERR! Linux 4.10.0-19-generic
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “run” "dev-proxy"
npm ERR! node v7.10.0
npm ERR! npm v4.2.0
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] dev-proxy: NODE_ENV=development ./node_modules/.bin/gulp proxy
npm ERR! spawn ENOENT
npm ERR! Failed at the [email protected] dev-proxy script ‘NODE_ENV=development ./node_modules/.bin/gulp proxy’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the blockstack-portal package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! NODE_ENV=development ./node_modules/.bin/gulp proxy
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs blockstack-portal
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR! npm owner ls blockstack-portal
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /home/mstroh/.npm/_logs/2017-06-03T22_58_08_900Z-debug.log
@jude and I took a look at the logs you were so kind to share with us this morning and determined that the fee problem you were experiencing is the result of how Blockstack estimates transaction fees. Adding more bitcoin has the effect of increasing the transaction fees such that you still don’t have enough bitcoin.
We’re working on a solution that will reduce the amount of those fees which should solve your problem. This will ship in the update released at the end of our current sprint (week from this coming Monday).