No version match ~0.2.0 on npm registry about karma-jasmine HOT 11 CLOSED

@tjwudi you still facing this ? seems to work nw.

from karma-jasmine.

I am using karma 0.12.0

$ karma --version                                                     
Karma version: 0.12.0

from karma-jasmine.

yup i am on the same version, seems to be fine.

from karma-jasmine.

Well, it does't work.. :(
just FYI, I am using OSX 10.9 and zsh shell.

from karma-jasmine.

can you try clearing npm cache

from karma-jasmine.

Works for me too...

$ npm install karma-jasmine@2_0

> [email protected] install /Users/vojta/Code/temp/node_modules/karma/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished

> [email protected] install /Users/vojta/Code/temp/node_modules/karma/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
[email protected] node_modules/karma
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected])

[email protected] node_modules/karma-jasmine

@tjwudi what command did you run? what is in your package.json?

from karma-jasmine.

https://www.npmjs.org/package/karma-jasmine still lists version 0.1.5

I've been using version 0.2.2 and enjoying it, but running npm-check-updates reports that version 0.1.5 is more recent than version 0.2.2 and if run with the -u flag will alter the package.json file back to version 0.1.5

When will the npm version be updated?

from karma-jasmine.

Hmm, effectively, there is something weird with the npm-published version. Running npm info karma-jasmine gives:

{ name: 'karma-jasmine',
  description: 'A Karma plugin - adapter for Jasmine testing framework.',
  'dist-tags': 
   { latest: '0.1.5',
     '2_0': '0.2.2' },
  versions: 
   [ '0.0.1',
     '0.0.2',
     '0.0.3',
     '0.1.0',
     '0.1.1',
     '0.1.2',
     '0.1.3',
     '0.1.4',
     '0.1.5',
     '0.2.0',
     '0.2.1',
     '0.2.2' ],

and my OsX it installs 0.1.5...

from karma-jasmine.

This is correct, no? The "latest" tag uses Jasmine 1.3, as that's still what most of the people use. If you want Jasmine 2, use "2_0" tag (which is 0.2.x version of karma-jasmine).

from karma-jasmine.

Oh, right, there is a 2_0 tag. I think we are all fine then. @tjwudi going to close this one as I don't see anything wrong / actionable at this point. Share your package.json (or ideally a minimal reproduce project) if you still face issues.

from karma-jasmine.

I solved this problem, it is because npm used proxy. I don't know why, though, I didn't ask it to use proxy. Simply run npm config set proxy null.

from karma-jasmine.