-
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
Remove GitHub dependency #3
Comments
What do you mean? |
The main difference for us would be that this would be usable for us at all. We are not able to clone from github, but we can pull down from NPM. For others, it would be that they can lock the version, and not get whatever is at the tip of your fork. Shrinkwrap will make the build reproducible |
Thank you for your good work!. Using the default version of jQuery work great. If I run karma without 'jquery-1.5.2' in the framework array all is fine.
/home/twhite/.nvm/v0.10.36/lib/node_modules/karma/node_modules/di/lib/injector.js:9 Any ideas? |
Sorry for the noise - I figured it out - karma-jquery do not include this version. |
SimenB, |
@bessdsv Sorry about the slow response In your dependencies, you reference your own fork of a project. https://github.com/bessdsv/karma-jasmine-jquery/blob/master/package.json#L32 What I'd like to happen is that you either make a PR back upstream to github.com/blittle/bower-installer, or publish your fork as a separate npm-module, to avoid having a git-dependency. Make sense? |
@SimenB |
Did you have any luck resolving this? It appears the bower.json file in the karma-jasmine-jquery package has bower-install as a dependency, but it doesn't allow for downloading this dependency using the https url, only the git protocol. As I am on a corporate network, I can't install this package. If I try git clone https://github.com/bessdsv/bower-installer.git it clones fine. However it appears that when npm tries to install karma-jasmine-jquery, it uses https, but when it gets to the bower-install dependency it only uses git - which fails. |
Nope, but we've upgraded to Jasmine@2, so we can use the |
Thanks for the tips here - added it as a reference in files, and all works great. |
@SimenB I'm having the same issue behind a firewall. Tried using jasmine-jquery straight up, but am getting an error during karma start. No provider for framework:jasmine-jquery. Did you or anyone else run into this? |
What does your config look like? |
module.exports = function(config) {
}) |
If you use |
Thats what it was. Thank you! |
👍 |
I have the same problem and I don't understand why this is (10 months later) still an issue. |
@bessdsv Can you replace protocol of bower-installer git dependency in your
to
https://github.com/bessdsv/karma-jasmine-jquery/blob/master/package.json |
Hi!
I work behind a firewall, and while packages from npm get through, your dependency on a fork on GitHub does not. Would it be possible to either get you fork's changes merged into the main project or publish your fork on the npm-repo?
The text was updated successfully, but these errors were encountered: