Error in NodeJS typings message Unable to find "-global" ("npm") in the registry

0

I get the following error in NodeJS :

ypings ERR! message Unable to find "–global" ("npm") in the registry.
typings ERR! message We could use your help adding these typings to the registry: sshttps:/./github.com/typings/registry
typings ERR! caused by https://api.typings.org/entries/npm/%E2%80%93global/versions/latest responded with 404, expected it to equal 200
typings ERR! 
typings ERR! cwd /Users/batman/desa2017/nodejs/batimovil
typings ERR! system Darwin 16.1.0
typings ERR! command "/usr/local/Cellar/node/6.9.1/bin/node" "/usr/local/bin/typings" "install" "dt~core-js" "--save" "–global"
typings ERR! node -v v6.9.1
typings ERR! typings -v 2.1.0
typings ERR! 
typings ERR! If you need help, you may report this error at:
typings ERR!   <https://github.com/typings/typings/issues>

npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/Cellar/node/6.9.1/bin/node" "/usr/local/bin/npm" "run" "typings" "--" "install" "dt~core-js" "--save" "–global"
npm ERR! node v6.9.1
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ typings: 'typings "install" "dt~core-js" "--save" "–global"'
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ typings script 'typings "install" "dt~core-js" "--save" "–global"'.
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  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typings "install" "dt~core-js" "--save" "–global"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs 
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls 
npm ERR! There is likely additional logging output above.
    
asked by abrahamstalin 16.02.2017 в 19:26
source

1 answer

0

Try with

typings install env~node --global

That message is not very friendly and gives no clue how to fix it. A user created an issue about this issue complaining about how cryptic the error is.

    
answered by 16.02.2017 в 19:41