Issue with npm start
See original GitHub issueI’m working through your series at the moment, still in the First Things First section, and I receive the following error when running npm start after cloning down the repo:
npm ERR! Darwin 16.3.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.9.2
npm ERR! npm v3.10.9
npm ERR! code ELIFECYCLE
npm ERR! product-management@1.0.0 start: `tsc && concurrently "tsc -w" "lite-server" `
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the product-management@1.0.0 start script 'tsc && concurrently "tsc -w" "lite-server" '.
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 product-management package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! tsc && concurrently "tsc -w" "lite-server"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs product-management
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls product-management
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/whoami/Documents/Code/Angular/angular2-gettingstarted/APM - Start/npm-debug.log
Computer-Name:APM - Start whoami$ sudo npm start
The following Stack Overflow answer solved the issue and the project starts just fine:
http://stackoverflow.com/a/37337795/2199064
Is this an issue with newer versions of Angular 2 or npm, or would this possibly be Mac specific? Might the line noted in the SO answer need to be updated within the project files? I’ve already done this and could submit it as a pull request if you’d like.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:9 (4 by maintainers)
Top Results From Across the Web
How to fix npm start command not working - Nathan Sebhastian
How to fix npm start command not working · Check if you have a package.json file in your project · Check if you...
Read more >npm start giving error in node.js - Stack Overflow
json . The package. json is telling npm that start means "run node ./bin/www". What happens when you run that same script from...
Read more >npm err! missing script: start Solution - Career Karma
If you type npm start and get the npm err! missing script: start error, there must be a missing line in the script...
Read more >npm-start - npm Docs
If the "scripts" object does not define a "start" property, npm will run node server.js . Note that this is different from the...
Read more >npm start not working, tried many solves :| #1328 - GitHub
derweili commented on Jan 17, 2019 · Delete the node_modules folder. · Open the package.json · Search for "gulp": "gulpjs/gulp#4.0", and replace it ......
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
Following an answer further down in the same SO link I provided earlier, I deleted the node_modules folder, cleared the local branch I made to then branch off a clean master from the original clone. I then re-ran npm install which worked just fine, and npm start worked perfectly after that. I believe I’m still sudo’d in my terminal, but everything seems to be running just fine with the configuration you’ve provided.
Thanks for your quick responses to this matter and for reaching out to external sources to help resolve it.
I just did.
Thank you
On Dec 28, 2016 3:21 PM, “Matt DeGoey” notifications@github.com wrote: