Tooling to capture data about candidate packages
wtrocki opened this issue · 5 comments
Originally posted by @mhdawson
As part of the discussion around which packages make sense to include in the architecture, it would be good to have overview data to supplement the direct experience of the team.
Informally we've looked at:
weekly npm downloads
PRs, rate of landing etc. active collaborators, etc. to assess how easy it will be to contribute to the project
It would be good to have some tooling to more easily gather this data, and it could be re-used to keep an ongoing eye on the packages we have included as suggested
Happy for us there are tools for this:
https://npmtrends.com/@nestjs/core-vs-hapi-vs-koa-vs-loopback-vs-fastify
https://npm-stat.com
This is a good start, but also I will look for usages in public repositories/red hat starters etc. and this is mainly a manual process. For the winning package is is great to take look on github insights to see how many PR's/issues were created closed etc. How much activity is there.
This is blocked by #20 - we have tool there that can use public API and give us some stats for packages etc. It is question if we like this tool etc.
For the modules in this repo that we are making recommendations for, we should think about extracting them into a separate file so that it will be easier to run some sort of tooling on them.
Yep this will be added to oratrix soon
We have the list of modules in https://github.com/nodeshift/nodejs-reference-architecture/blob/main/npcheck.json
Good to close