npm run dev Issue
See original GitHub issueSystem: plain Virtual Box Ubuntu installation. With Ubuntu 16.04.2 LTS Shure I’ve installed all necessary packages (newest release): git, pip, npm, virtualenv, node.js
After that I’ve followed @larrysalibra instructions:
apt-get update && sudo apt-get install -y python-pip python-dev libssl-dev libffi-dev rng-tools libgmp3-dev
virtualenv -p /usr/bin/python2.7 blockstack
source blockstack/bin/activate
pip install git+https://github.com/blockstack/virtualchain.git@rc-0.14.1 git+https://github.com/blockstack/blockstack-profiles-py.git@rc-0.14.1 git+https://github.com/blockstack/dns-zone-file-py.git@rc-0.14.1
pip install git+https://github.com/blockstack/blockstack-core.git@089d436caea79919296fbc05d6d46e5e52b57d6c
That worked fine and after thatblockstack setup
and blockstack api start
also worked fine. And localhost showed some Infos and no Error. So Step 1 was completed.
After that:
(blockstack) test@test-VirtualBox:~/blockstack-browser$ npm install
worked fine. After that:
(blockstack) test@test-VirtualBox:~/blockstack-browser$ npm run dev
but this step crashes and i get the error Code:
npm ERR! Linux 4.4.0-31-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "dev"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code ELIFECYCLE
npm ERR! blockstack-portal@0.4.0 dev: `concurrently --kill-others "npm run dev-ui" "npm run dev-proxy"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the blockstack-portal@0.4.0 dev script 'concurrently --kill-others "npm run dev-ui" "npm run dev-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! concurrently --kill-others "npm run dev-ui" "npm run dev-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/test/blockstack-browser/npm-debug.log
Thanks for your help!
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
npm run dev not working - Stack Overflow
I have a problem with vueJs webpack, I want to run on the server, with a command: npm run dev. But I get...
Read more >npm ERR! Missing script: "dev" [Solved] | bobbyhadz
To solve the npm ERR! Missing script: "dev" error, make sure to add a dev command to the scripts object in your package.json...
Read more >What to do when "npm run dev" is not working? (React)
I tried to start my application with “npm run dev” as it is a react / next.js app. The console gave me an...
Read more >npm run dev error - Laracasts
Failed at the @ development script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above....
Read more >npm run dev Is Not Working In Laravel 8 - Error Fixed - YouTube
You will fix your error InchaeAllah in four steps, don't worry Music:https://www.youtube.com/watch?v=AOeY-nDp7hI&t=0s.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Skorpion7777 Thanks so much for the very detailed response and giving it another go!
You’ll need to make sure that your Blockstack Core API endpoint is running at the location the Portal expects. By default this should be localhost:6270. You can check the Portal API settings in the Account app and also check the network requests box of the developers tools to see where requests are going and if they’re being answered by Core.
this seems to be resolved.