Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Bundlephobia badges unreliable, returning 429 #652

Open
robinloeffel opened this issue Dec 18, 2023 · 3 comments
Open

[Bug] Bundlephobia badges unreliable, returning 429 #652

robinloeffel opened this issue Dec 18, 2023 · 3 comments

Comments

@robinloeffel
Copy link

robinloeffel commented Dec 18, 2023

Hey there! I've recently made the switch for some of my packages from shields.io to badgen.net. I'm really happy with it, especially with the load times and the variety of available services!

However, speaking of those services, bundlephobia.com has been notoriously unstable ever since for my packages. Sometimes the badges correctly work, but sometimes I get returned a badge just saying "bundlephobia 429", even though the service itself works fine when accessing it directly. You can see it happening in the following readmes:

And here some screenshots in case both instances are working when you get the time to check out this issue.

Screenshot 2023-12-18 at 11 59 52
Screenshot 2023-12-18 at 12 00 07
Screenshot 2023-12-18 at 12 00 21

Hope you have a good one, and thanks for all of your work!

@josephwynn-sc
Copy link

I was having this issue as well, and ended up switching back to shields.io. I could never figure out why badgen.net has an issue with some of my packages.

@franciscop
Copy link

I just did an experiment. I believe if Bundlephobia does not have a package indexed (never searched) and you try to use badgen, it will error out, and even if you index it later it retains the error. However if you go to bundlephobia first and then use badgen, it will work

@franciscop
Copy link

Update: if you add the ?cache=300, load it, and wait the 5 mins then it will work again.

Or maybe it was all chance, who knows, but this way it started working for me at least!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants