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: I don't think it's a parsing error. I've pulled in all the latest changes (not the JSON one, obviously) and tried several refreshes and it seems fine. The refresh actually failed once (and gave an error/reverted to the old results, as expected) but I think the repo's been flaky for the past 12 hours or so as I had issues installing packages at random earlier.
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: I don't think it's a parsing error. I've pulled in all the latest changes (not the JSON one, obviously) and tried several refreshes and it seems fine. The refresh actually failed once (and gave an error/reverted to the old results, as expected) but I think the repo's been flaky for the past 12 hours or so as I had issues installing packages at random earlier.