I published the package on npm and I want to display the badges. Of the three icons, only one returns with an error:
Hi. We request download stats from NPM using a call to https://api.npmjs.org/downloads/range/ Usually if we call something like https://api.npmjs.org/downloads/range/1000-01-01:3000-01-01/localeval that will return some stats. In the case of your package, if we call https://api.npmjs.org/downloads/range/1000-01-01:3000-01-01/dealers-fontface that is returning an error, so that is what the badge reports.
It looks like you've only published this today. I don't know the NPM API in much detail, but maybe there is some caching or it needs a full day's worth of data before it will give a response on that endpoint? If the problem doesn't resolve itself, maybe open an issue with NPM.
@chris48s I published the package yesterday, but the day has not passed. Got it. I'll wait for the cache update. Thank you!
Probably we should return package not found…
Has the package been removed? I can't quite make sense of what's happening right now.
@paulmelnikow
Oh! Sorry, I today renamed my package to official-fontface, because he was conceived as a repository of official fonts of various companies, but, by mistake, called it as dealer fonts.
I updated my first message.
Gotcha! Yea, we're showing some odd stuff for your old package. Deleting a package happens so rarely so I'm not too concerned about it. But publishing new packages happens all the time, so I updated the message that appears in that case. See #1892.
Not, when I described the problem, the package was available by the old name - it was published yesterday.
The name changed only tonight.
I'm 90% sure I understand. 😀 I think showing "too new" on the downloads badge is a pretty good way for us to handle this.
I agree. The option is excellent.
(I translate into English via Google Translate.)
Most helpful comment
I'm 90% sure I understand. 😀 I think showing "too new" on the downloads badge is a pretty good way for us to handle this.