Doesn't update

[vitaly-t]

Just how often does David update? I've fixed dependencies 2 hours ago, and they still come up as out of date, while David uses the old package.json.

Is there something extra I need to do or it just doesn't work?

[vitaly-t]

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

[alanshaw]

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.

[seriema]

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 grunt-contrib-imagemin@0.9.2 but the latest is actually 0.9.4 (published four months ago).

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

[alanshaw]

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

[seriema]

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

[alanshaw]

That's up to date according to your range

[seriema]

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.

[seriema]

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?

[alanshaw]

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.

[seriema]

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.