Doesn't update about david HOT 10 OPEN

UPDATE: It did update, 3 hours later. That's not fast enough. Is there a way to make it happen faster?

from david.

I think it's a bug see alanshaw/david-www#178. I haven't got time to fix this right now but would appreciate a pull request.

from david.

Not sure if this is the same thing, but when I run david it reports All dependencies up to date. Yet if I do npm list I can see [email protected] but the latest is actually 0.9.4 (published four months ago).

I tried david u -u but it didn't do anything.

from david.

What does the entry for grunt-contrib-imagemin look like in your package.json?

from david.

"grunt-contrib-imagemin": "^0.9.2",

from david.

That's up to date according to your range

from david.

Not sure I understood. On npm the latest is 0.9.4, but I can't get david to grab it when I run david update. It thinks that 0.9.2 is the latest, when it clearly isn't and 0.9.4 should be a valid update.

from david.

This is still happening and either David doesn't work as I think or .. I don't know. I have "karma": "^0.13.2", in my package.json. When I run david update I'm expecting it to update to 0.13.8 but it doesn't. Running npm update updates it so I'm expecting David should too?

from david.

Fair point, but as you say npm update updates your existing dependencies within the range of versions stated in your package.json. David's purpose has always been to identify and install dependencies who's versions are higher than the version range stated in your package.json.

from david.

Ah... I've missed that distinction. The David website marks any dependency out of date. Maybe that's the difference between the yellow and red badge? If it's within range or not? I thought it had to do with minor vs major version.

from david.