Describe the bug
For example, the package size of oxlint has decreased in newer versions, but if you look at the "alpha" version (v1.17.0-alpha.0) from a few months ago, it shows as though the package is increasing in size, because the "before" version it's using for comparison is the newest version, 1.57.0: https://npmx.dev/package/oxlint/v/1.17.0-alpha.0
Additional context
v1.17.0-alpha.0, September 2025: 19.7 MB
v1.57.0, March 2026: 14.9 MB
Ideally, npmx would not display a warning when viewing the old alpha version. This is maybe due to some weirdness in how version comparison works in semver? I'm not really sure.
Logs
Describe the bug
For example, the package size of oxlint has decreased in newer versions, but if you look at the "alpha" version (v1.17.0-alpha.0) from a few months ago, it shows as though the package is increasing in size, because the "before" version it's using for comparison is the newest version,
1.57.0: https://npmx.dev/package/oxlint/v/1.17.0-alpha.0Additional context
v1.17.0-alpha.0, September 2025: 19.7 MBv1.57.0, March 2026: 14.9 MBIdeally, npmx would not display a warning when viewing the old alpha version. This is maybe due to some weirdness in how version comparison works in semver? I'm not really sure.
Logs