0.3.0 about minimatch HOT 13 CLOSED

Ah, looks like the push had failed. Thanks, all set now.

from minimatch.

Still get errors when I try to install module that depends on version ^0.3.0

npm http 200 https://registry.npmjs.org/minimatch
npm ERR! Error: No compatible version found: minimatch@'^0.3.0'
npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.0.2","0.0.4","0.0.5","0.1.1","0.1.2","0.1.3","0.1.4","0.1.5","0.2.0","0.2.2","0.2.3","0.2.4","0.2.5","0.2.6","0.2.7","0.2.8","0.2.9","0.2.10","0.2.11","0.2.12","0.2.13","0.2.14","0.3.0"]
npm ERR!     at installTargetsError (/private/var/tmp/nodeenv-0.8.25/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR!     at /private/var/tmp/nodeenv-0.8.25/lib/node_modules/npm/lib/cache.js:641:10
npm ERR!     at saved (/private/var/tmp/nodeenv-0.8.25/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>

from minimatch.

@eskimoblood upgrade npm

from minimatch.

@sindresorhus, sorry I'm not that deep into this stuff, what to you mean with upgrade npm?

from minimatch.

http://bit.ly/Sd4zrj

from minimatch.

when you have a central build server that multiple teams depend on the answer of just upgrade npm isnt a great one. Something changed somewhere is there any idea?

from minimatch.

This was our problem as well. We could fix it by bumping the node version for our build system from 8 to 10. Don't know why but it fixed the issues.

from minimatch.

this is part of a very large system for a very large company. throwing a major update like that to solve a small issue is not a good solution

from minimatch.

I am also having this problem. And I can't just update npm or node because that would require weeks of regression testing the code.

Isn't there a fix that would fix the real problem?

from minimatch.

In the middle of 2013, support for the ^ semver operator was added to npm. A few months ago, it became the default.

This wasn't added to Node 0.8, because that version of Node is no longer updated.

If you can't update things, then why are you updating the thing that depends on minimatch? It seems weird that one piece is a year behind, but another is updating to the latest and greatest. It's pretty common for new versions of libs to rely on features that have been in the underlying platforms for a year.

from minimatch.

I am running into this during my Travis CI builds for node 0.8 and tried to fix it by adding:

before_install:
  - npm update -g npm

However, I'm now getting this error during that update

npm ERR! Error: No compatible version found: inflight@'^1.0.1'

Which basically means I'm hosed?

EDIT: Found related issue on npm project (npm/npm#5318)

from minimatch.

@jgable The latest glob 3.x doesn't use ^. The latest npm release does not use ^ for inflight (and also bundles inflight). Everything should work fine by default now, unless you're relying on glob@* or something crazy like that.

from minimatch.

I 'm running into this as well, two weeks ago the build worked, and now it doesn't due to this. is there no way to fix this without upgrading all of node?

from minimatch.