Badgen.net: Error badges on chorme web store

Created on 15 Apr 2020  路  9Comments  路  Source: badgen/badgen.net

Most helpful comment

Published the new method in v1.4.0 as .version() :tada:

All 9 comments

@crimx Thanks for reporting

@amio is this fix still to be released? I'm still getting 5xx responses

Examples

store listing
badge link

Screenshots

Screenshot 2020-05-07 at 15 07 48
Screenshot 2020-05-07 at 15 08 03

@andyrichardson it was fixed and released, it's broken again. Here's the fix https://github.com/simov/chrome-webstore/pull/2

Instead of waiting PR being merged every time it seems like you can just pass the version as function argument.

Also the version can be teased out directly from the html. How about adding a script that checks the version daily? I can help if you want to give it a spin.

pass the version as function argument

馃憤

adding a script that checks the version daily?

Badgen is stateless, we cannot store/cache this version info. We could make it a standalone api with cdn cache, like a https://latest-chrome-webstore-api-version.now.sh just responses 20200420 , but I guess two serial requests for generating a badge would hurt some performance and stability.

Is there a way to be notified when the webstore api is broken? So that the version can be updated with Badgen.

Thought about making a cron job with GitHub Actions to check api availability, a failed execution would leave a notification on GitHub.

PS, we can even make a status page base on this 馃槀

That should work. Though ideally the Action should just automatically update Badgen with the new version when broken.

I've submitted a PR to chrome-webstore.

Published the new method in v1.4.0 as .version() :tada:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

styfle picture styfle  路  5Comments

tunnckoCore picture tunnckoCore  路  3Comments

amio picture amio  路  3Comments

shellscape picture shellscape  路  4Comments

madnight picture madnight  路  5Comments