-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot install from npm [windows] #8
Comments
were you able to resolve this? |
This is probably related to issue #3, there is a git dependency to Bessdsv's fork of bower-installer, which (as far as I can tell) is no longer necessary given the resolution of the issue upstream in blittle/bower-installer via PR's 62 and 101. My solution (issue with an internal firewall) was to publish a fork without that dependency internally and so far that seems to be working fine. |
same problem on Windows 7. log:
|
I am having the same issue on windows 7 too. npm WARN npm ERR! System Windows_NT 6.1.7601 |
removed unneeded bower dependency. bessdsv#8
I have this issue on OSX as well |
Since the pull request to fix the issue has been sitting untouched for months, a fork has been made with the fix. See details here: #10 Branch here: https://github.com/AStoker/karma-jasmine-jquery/ Via npm and Bower, it was registered under the name |
bessdsv/karma-jasmine-jquery#8 reveals that windows users are going to be stuck without this until: 1)The dependency issues are fixed. 2) configuration within git to prefer "https://" over "git://" (really: ssh+git) links are honored in git, bower and npm. 3) a workaround to settings to avoid the failure of git ls-remote calls against a "git://" protocol link As I am using cygwin, I didn't want to go down this path as I may just be revealing a larger issue within either of the above tool's issues with cygwin path issues? Who knows. . . Tested on: windows 7 (x86_64) node.js version: 8.12.0 npm version: 6.4.1 behind a corporate proxy
hi Guys,
I'm trying to install this package via npm but have no luck. it always say can't connect to github. I have my git config global set to use https instead of git protocol and in fact npm install other packages works only this package. Am I missing something? or is there any workaround on this aside from direct cloning?
Thanks
The text was updated successfully, but these errors were encountered: