[Feature Request] Data-only API endpoint

[PFiS1737]

I suggest providing a data-only API endpoint.

It could use a dedicated route (such as api/top-langs-data) or a query parameter (such as api/top-langs?data_only=true).

These would return the raw json data from the fetchers, rather than SVG.

Users could then build their own renderers to visualize the data.

Furthermore, we could consider refactoring the fetchers into independent package, allowing users to install and use them via npm.

[martin-mfg]

Can you tell us more about what you want to do?

Also, would it make sense for your use case to fetch the specific data you need directly from GitHub's APIs? Or to fork github-stats-extended and change the rendering logic according to your needs?

[PFiS1737]

I want to use this data in my blog (during SSR).

If there were a data API endpoint, I could simply request a single URL to get the data I need, without having to deal with complex GitHub authentication and GraphQL code generation.

Modifying this repository is not suitable for me, because my rendering workflow needs to be integrated into my blog generator.

[martin-mfg]

Unless there is more demand for a data-only endpoint, it's not a priority for this project.

But you should be able to extract the data you need from a generated SVG with a regular XML parser. For example you could request https://github-stats-extended.vercel.app/api?username=PFiS1737&include_all_commits=true, parse the returned XML, and then use XPath with the query /svg/g[2]/svg/g[1]/g/text[2] to to get your star count.

Please share your result, I am curious to see how you embedded your stats in your blog!