This plugin doesn't support Window system?
jankerli opened this issue · comments
the error code like this:
npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/ariya/esprima) undefined
npm WARN `git config --get remote.origin.url` returned wrong result (git://githu
b.com/ariya/esprima) undefined
npm WARN `git config --get remote.origin.url` returned wrong result (git@github.
com:ariya/esprima) undefined
npm WARN `git config --get remote.origin.url` returned wrong result (git@github.
com:ariya/esprima) undefined
npm ERR! git clone git@github.com:ariya/esprima undefined
npm ERR! git clone git@github.com:ariya/esprima undefined
npm ERR! notarget No compatible version found: esprima@'ariya/esprima#harmony'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["1.1.0","0.7.0","0.8.0","0.8.1","0.8.2","0.9.0","0.9.1","0.9.
2","0.9.3","0.9.4","0.9.5","0.9.6","0.9.7","0.9.8","0.9.9","1.0.0","1.0.1","1.0.
2","1.0.3","1.0.4","1.1.0","1.1.1","1.2.0","1.2.1","1.2.2"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "D:\\Program Files\\nodejs\\\\node.exe" "D:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "jsfmt"
npm ERR! cwd C:\Users\Administrator
npm ERR! node -v v0.10.31
npm ERR! npm -v 1.4.23
npm ERR! code ETARGET
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\Administrator\npm-debug.log
npm ERR! not ok code 0
I resolved it.
:)
ehm, please: how did you solve it? We're having similar errors with another plugin that uses esprima as well. Thanks.
@BrainCrumbz you should only get something like that if you try to do an npm install
fmtjs already comes with all the npm modules installed.
Please make sure you have the latest version on node installed on your computer and everything should be fine.
thanks for feedback. Actually we are in a complete different situation, not at all related to sublime-jsfmt (sorry, I didn't even know about its existence until now).
It's just the we had exactly the same initial error messages while updating another npm package, for one of our projects.
We re-installed Git (on Windows 64) and pointed to the newly installed executable, and now that error is gone.
Cheer