Closed pdehaan closed 8 years ago
Here's some really crude output from my test script. There are definitely a few unexpected results which I can't reproduce w/ fetch-nice-package so I think the https://registry.npmjs.org/-/all/static/today.json endpoint may be returning some funny data, or my code is most certainly buggy.
But you can see a bunch of invalid repos which don't deserve to parse, or a few bitbucket/gitlab repos. Plus a few extra random apache.org results.
Thanks for reporting. non-GitHub repository data is now kept intact as of 1.2.2
... which is a fair assumption, but I'm seeing some cases in my :poop::fire: https://github.com/pdehaan/npm-today repo where recently published modules may be gitlab or bitbucket or other random Git repos (or just random garbage).
Not sure if it's worth fixing, but a bit inconvenient when a user specifies a valid repo URL and after normalizing it through nice-package, it comes back
null
.Example:
Output:
Yet, it we look at http://npm.im/conventional-gitlab-releaser we can see npm sees the repository, and the package.json specifies a valid value at https://gitlab.com/hutson/conventional-gitlab-releaser/blob/master/package.json#L37-40
Not sure if there is an easy way to have it return the original package.json repository.url (if there was one), if the parser wasn't able to parse the
repository
-- although that means that you'd potentially be getting back different keys depending on what repository people used.