Unexpected end of JSON input while parsing when installing vue-cli
See original GitHub issueWhen i try to install vue-cli via npm i get the following error.
C:\Users\yomal.ds\Desktop\VueJS>npm install --global vue-cli
npm ERR! Unexpected end of JSON input while parsing near '...},"dist":{"shasum": "8'
npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\yomal.ds\AppData\Roaming\npm-cache\_logs\2017-09-12T06_55_ 53_890Z-debug.log
I tried npm cache clean and reinstalling npm. Debug log is attached. Log.txt
OS : Win 7 x64 npm : v5.4.1 Node : v8.0.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (3 by maintainers)
Top Results From Across the Web
vue.js - How to fix "npm ERR! Unexpected end of JSON input ...
1 - Run your Command Invite/Terminal as Administrator. 2 - Install the Vue CLI globally with the command : npm install -g vue-cli....
Read more >How to fix "npm ERR! Unexpected end of JSON input while ...
Unexpected end of JSON input while parsing " on Vue CLI installation. I want to install Vue CLI . and i run this...
Read more >[SOLVED] npm ERR! Unexpected end of JSON input while ...
This video is helpful to those people who are getting problems while installing the vue.js or Angular.js. We solved the npm ERR! Unexpected...
Read more >npm ERR! Unexpected end of JSON input while parsing near
Unexpected end of JSON input while parsing near. There's a high chance that your npm cache been damaged.
Read more >Unexpected end of JSON input while parsing near '...":"
Try to create a new vue project using vue cli please me understand this error, Unexpected end of JSON input while parsing near...
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
npm cache clean --force
also helps
Downgrading to npm v5.3 worked for me. It’s a npm 5.4 bug https://github.com/npm/npm/issues/18380