Skip to content

Loading…

Release on npm #183

Closed
cburgmer opened this Issue · 22 comments
@cburgmer

It would be nice if jasmine-jquery was available over npm. Currently only some old fork is available there.

@andreypopp

Second that, I've just wasted 10 min of trying to use getJSONFixture with old fork from npm.

@Miw0

+1

@tony

@velesin ? publish?

@ryanwalters

+1 jasmine-jquery@1.3.3 makes me sad. @velesin Time to publish!

@travisjeffery
Collaborator

i doubt the lib would work as is, so there'd be some code that would need writing. i wouldn't use this. if someone wants to actually submit a pr. i'd take a look.

@daviesgeek

+1
I spent so much time trying to get it to work, and ended up that I installed it via npm

@TimotheeJeannin

+1
It would be great to to have this published on npm !

@Nate-Wilkins

Well technically you could just pull it right from the repo with npm

npm install git+https://github.com/velesin/jasmine-jquery

@necolas

Came here to report this issue after working on some twitter projects.

@just-boris

+1
Good library! I'd like to see it in npm

@gajus

Should be on NPM. Here is a 2 minutes guide how to do it, https://gist.github.com/coolaj86/1318304.

@just-boris

The name jasmine-jquery already taken by @dkastner
@dkastner, you keep fork of this repo in npm, please update it or provide rights to this repository owner

@just-boris

To others: now you can install this package using the direct link:

npm install git+https://git@github.com/velesin/jasmine-jquery.git#2.0.5
@gajus

It makes no difference what is the name of the library. Call it velesin-jasmine-jquery.

@dkastner

I will remove my package

@dkastner

Unpublished!

@varemenos

Is this issue still valid?

@Nate-Wilkins

@dkastner Thanks!

@varemenos I don't think so

@WouterJ

The latest 2.1 version is not available on NPM

@alexandernst

+1, can we get 2.1.0 in npm?

@travisjeffery
Collaborator

Just published 2.1.0 to npm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.