Bad Package Versions

[DamonOehlman]

As we've seen before some semver strings tend to cause npmd to bail out. I've encountered the following this time around:

Error: package:grunt@0.4.1 could not resolve underscore.string@~2.2.0rc
Error: package:ws@0.4.25 could not resolve options@latest
Error: package:streamws@0.1.1 could not resolve options@latest

I might hit a couple more and if I do I'll add them in comments. It's been pretty smooth sailing so far though - thanks for all the work you've put in on this :)

[DamonOehlman]

Also, this project seems to be one that doesn't like being installed using npmd:

https://github.com/jkroso/progress-svg

From what I can tell it's this package require (someway down the dependency tree) that causes the issue:

git://github.com/nathan7/inherit#f1a75b48444d2637725d42be23be21c31c296c35

An npm install rather than an npmd install works ok.

[dominictarr]

Ah, okay I see why... right these urls a slightly different format that I normally see, I've fixed this... but need to shift a few things around...

[dominictarr]

Okay this is fixed in npmd@1.1.2 can now do npmd install progress-svg --dev (that is where the problems where coming from) and it will work.

[DamonOehlman]

Worked a treat - thanks :)

[dominictarr]

okay, I made a simple integration test that runs npmd resolve on modules that have caused problems in the past. If you find any more please ping me and I'll add them!

[DamonOehlman]

Will do mate - thanks.