Installing vue-cli I get the error ENOVERSION - No valid versions available for timed-out
See original GitHub issueInstalling vue-cli I get this error.
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for timed-out
I got before that error, the following one, but it disappeared when I updated node and npm.
npm ERR! code ENOVERSIONS npm ERR! No valid versions available for duplexer3
I have check the requisites for installation and I think this is not the problem.
npm --v = 5.5.1
node -v = v8.9.1
graphcool version = 0.4.9 //required
I’m using windows 10 with powershell in Visual Studio Code.
Attached the debug log.
2018-01-06T19_27_05_478Z-debug.log
Thanks.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6
Top Results From Across the Web
Installing vue-cli I get the error ENOVERSION - No valid versions ...
Installing vue -cli I get the error ENOVERSION - No valid versions available for timed-out.
Read more >nodemon install error "No valid versions available for timed-out"
npm ERR! code ENOVERSIONS npm ERR! No valid versions available for timed-out npm ERR! A complete log of this run can be found...
Read more >Installation | Vue CLI
You can verify that it is properly installed by simply running vue , which should present you with a help message listing all...
Read more >Troubleshooting - Vue CLI
This document covers some common Vue CLI issues and how to resolve them. You should always follow these steps before opening a new...
Read more >Configuration Reference | Vue CLI
Note the target directory contents will be removed before building (this behavior can be disabled by passing --no-clean when building). TIP.
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
@troneras @hjJunior @nats-afs @michaeljaekel @neves This is due to npm registry issue: See https://github.com/npm/registry/issues/255
works again like expected. Thanks.