Open jonathantneal opened 7 years ago
@ben-eb had a suggestion to periodically query the npm registry ourselves. That would add a minor adjustment to the instructions.
https://registry.npmjs.org/-/_view/byKeyword?startkey=[%22postcss-plugin%22]&endkey=[%22postcss-plugin%22,{}]&group_level=2
:
result.rows.map(
(row) => row.key[1]
)
entry
data from NPM...We might also use the dependencies
object to validate whether PostCSS is summoned.
I’d like to recommend an updated list of data we should collect for plugins and how we should collect it.
name
:process.argv[2]
, the first argument passed to the script.entry
data from NPM:https://registry.npmjs.org/${ name }/latest
:author
, the primary author.dependencies
, all/plugin dependencies.keywords
, additional search terms.categories
, plugin category terms:repo
, the GitHub repository path:https://api.npmjs.org/downloads/range/1000-01-01:2100-01-01/${ name }
:downloads
, the total number of downloads:entry
data from GitHub:https://api.github.com/repos/${ repo }
:stars
, the number of stars (fromstargazers_count
).forks
, the number of forks.issues
, the number of open issues (fromopen_issues_count
).https://api.github.com/repos/${ repo }/contributors
:contributors
, the list of contributors:user
, a contributor’s username (fromlogin
).contributions
, a contributor’s number of contributions.avatar
, a contributor’s avatar (fromavatar_url
).entry
data to the database byname
.