Package page defaults to non-latest version after a new release

[nicolo-ribaudo]

Describe the bug

I just released babel-loader v10.1.1. It correctly shows up as "latest" in the sidebar, but the version at the top for the package page still defaults to 10.1.0.

I also tried in a private window to make sure it wasn't a client-side caching problem.

Additional context

No response

Logs

[ShroXd]

I did some investigation on the source code, and I think this bug is caused by different data sources.

The version at the top of the package page is fetched from https://npm.antfu.dev/<pkg>, but the version list and sidebar are fetched from the npm registry. Looks like npm.antfu.dev is cached, so it may take more time to update.

A simple fix would be adding a watcher in the npmx package page component, and once the version at the top of the page is outdated, replace it with the latest version from the npm registry.

But I don't think this is a good solution — there should be a single source of truth for package information. I'm not sure if the npmx team has made any decision about this, or if the version list from npm is just a temporary solution. So it would be better to let the npmx team weigh in on this.

[alex-key]

I think I know the root cause - the logic behind requested and resolved version on package page should be improved. I'll work on a fix