[FEATURES] add additional information for a package
See original GitHub issueHi guys. I’ve got requests for some new additions to the npm-search
index. Let’s discuss them here:
- open issues on gihtub: How many open issues are there.
- number of gihtub stars: How many people stared this projet.
- number of gihtub forks: How many people stared this projet.
- open PR on gihtub: How many open PRs are there.
- last commit on gihtub: When was the last commit on master.
- add any other usefull information (here are all the properties returned by Github’s API)
Does this make sense?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Features On Demand
Features on Demand (FODs) are Windows features that can be added at any time. Common features include language resources like handwriting ...
Read more >Easily track your packages with new Gmail features
New Gmail features make it easier to track your packages. ... view of your package tracking and delivery information right in your inbox....
Read more >Features - The Cargo Book
Features. Cargo "features" provide a mechanism to express conditional compilation and optional dependencies. A package defines a set of named features in ...
Read more >The Ultimate Guide to Product Packaging
Learn how to design beautiful packaging for your products that builds customer loyalty and drives retention in your online store.
Read more >Buy additional app features with in-app purchases and ...
What is a consumable in-app purchase? · Game currency, such as coins or gems · Extra health points in a game · A...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Those are valid concerns, adding the jsDelivr downloads seems “easy”. As for the GitHub api requests that’s a bit more tricky because of what @Haroenv said. Then you also have the freshness issue, currently rebuild the full index every week. If we provide things like number of opened issues, you might want the data to be a little fresher. That might require a bit more work to optimise the data pipeline (today it takes one day to rebuild completely the index, I am sure we can lower it down but we never investigated it too much)
Still, if you already have ideas on how to do it well, please do contribute, make it faster, anything 😃
Thanks for the nice architecture thoughts!
I did try out the GitHub GraphQL API, a bit strange at the beginning (I had to understand the actual GraphQL language), but afterwards feels super nice.
Example: https://github.com/vvo/zorgs/blob/master/src/zorgs/src/queries/repositoriesWithCommits.js