Bug in badges with scoped packages about badgen.net

[amio]

👆 Should add this to knowledge base.

[amio]

Weird, @nestjs/core/* stop working for me now 🤔

I used to get latest from full meta list, then turn to that tricky method(use /* to get latest only) to reduce response size, seems we need to go back again 🤨

[tunnckoCore]

No problem, i'm working on that.

[tunnckoCore]

just a note for curious devs working with the NPM API:
endpoint registry.npmjs.org/[pkg-name]

a) with scoped packages there is no /latest, but have /dist-tag-name
b) for not scoped ones is exactly the opposite - there IS /latest, but not have /dist-tag-name

pahahahaha

[tunnckoCore]

So.. it seems the api currently works as expected both for scoped and non-scoped ones?

So we can just request registry.npmjs.org/[pkg-name]

and get dist-tag field, and get version from there dist-tag.latest by default.

[tunnckoCore]

AHA! Got it... /latest does not work for the scoped ones :D

[tunnckoCore]

The interesting thing in that API is that the problem is only when /latest otherwise it works for other tags like /@nestjs/core/next 😆 but not for /@nestjs/core/latest.

[tunnckoCore]

Watafak /next gives me error (get not allowed method), no matter what package (except scoped ones).. 🤣

[amio]

😂npm registry:

[tunnckoCore]

hahaaha

[tunnckoCore]

I don't know how some people build such APIs ;d

[tunnckoCore]

Just realized, that if you want to get another tag, you just can do it with another endpoint, like it is able for the latest tag.

So in case we recieve different than latest, we will trigger (only then) the full metadata and get it from dist-tags...