Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

`npm install jasmine-core` installs different contents for same version #608

Closed
cburgmer opened this Issue · 6 comments

4 participants

@cburgmer

Installing jasmine-core through npm on a Mac OSX and Ubuntu 13.10 (on a virtual machine) yields different contents for version 2.0.0.

The Mac OSX version seems to have the more recent contents including line https://github.com/pivotal/jasmine/blob/master/lib/jasmine-core/jasmine.js#L1206 whereas the Ubuntu installation does not.

As a result the code I am looking at fails on Ubuntu but works on Mac OSX.

I am trying to debug this issue further, but so far am stuck with npm repeatedly installing the same specific content, even after clearing the caches.

@cburgmer cburgmer referenced this issue in HumbleSoftware/js-imagediff
Merged

Jasmine2 fix #37

@infews
Owner

Thanks for finding this. We'll take a look and see what's going on. Very odd.

@infews
Owner

I've created a bug in our Tracker backlog.

@briandipalma

@cburgmer There doesn't seem to be an easy way to use jasmine from node anyway. I'm a bit shocked to find that installing it via npm doesn't create a bin entry in my node_modules so that I can't just do npm t when I add jasmine to the test scripts key.

Is out of the box support for node really that weak? mocha seem to have done the right thing...

@cburgmer

I am unsure now whether this is connected to jasmine. One goal of raising this ticket here was to find out whether there was a pre-release upload to npm.

Right now I believe that npm might have used a locally cached version of an older git checkout installed over npm using the git URL. I sadly haven't sat down to further debug this behaviour, especially as I've nuked the cache on my OSX system believing that the Ubuntu installation was at fault (and so trying to maintain the version for debugging purposes there).

@slackersoft
Owner

I'm not sure how we would go about trying to reproduce this. Are you still seeing the issue? If not, can we close this?

@slackersoft slackersoft added the waiting label
@cburgmer

This is probably much more an issue with npm.

@cburgmer cburgmer closed this
@infews infews removed the ready label
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.