Looks like every item in the npm Package Manager dialog has `(This package has no keywords.)` line.
Is that statement accurate or is the parsing of keywords not working correctly?
If it's parsing correctly, and these packages really don't have any keywords, then I think we should get rid of that line. It's not valuable enough (I couldn't find a package that has keywords) and makes each entry in the list taller than necessary.
Edit: It may be a problem with parsing, because they all show version 0.0.0
Comments: Should all be fixed as of https://nodejstools.codeplex.com/SourceControl/network/forks/BartRead/rgnpm01/changeset/307acd79c4730dc5fc5d3a2d94aab2c125443916. I've modified the parsing to handle npm search output both pre 1.4.3 and from 1.4.3 onwards. I've also added more tests for 1.4.3 and later, to deal with a lot of extra corner cases and weirdness (names split across lines, missing fields, truncated versions, etc.), and split up the existing tests more to provide finer grained coverage of the parsing. Unfortunately we'll continue to be sensitive to changes in this output format so I'd suggest more tests will need to be added as new versions of npm are released. This is a PITA because I'm not aware of any other way to get a complete list of packages at present. Still, for now, it's fixed. Resolving this bug.
Is that statement accurate or is the parsing of keywords not working correctly?
If it's parsing correctly, and these packages really don't have any keywords, then I think we should get rid of that line. It's not valuable enough (I couldn't find a package that has keywords) and makes each entry in the list taller than necessary.
Edit: It may be a problem with parsing, because they all show version 0.0.0
Comments: Should all be fixed as of https://nodejstools.codeplex.com/SourceControl/network/forks/BartRead/rgnpm01/changeset/307acd79c4730dc5fc5d3a2d94aab2c125443916. I've modified the parsing to handle npm search output both pre 1.4.3 and from 1.4.3 onwards. I've also added more tests for 1.4.3 and later, to deal with a lot of extra corner cases and weirdness (names split across lines, missing fields, truncated versions, etc.), and split up the existing tests more to provide finer grained coverage of the parsing. Unfortunately we'll continue to be sensitive to changes in this output format so I'd suggest more tests will need to be added as new versions of npm are released. This is a PITA because I'm not aware of any other way to get a complete list of packages at present. Still, for now, it's fixed. Resolving this bug.