Repository navigation
Timeline: improve stable-only view #3075
Description
Describe the feature
The timeline view, filtered down to "stable-only", does not work well if a package publishes many non-stable releases.
Example: https://npmx.dev/package-timeline/sanity/v/6.5.0
In this case, "stable-only" only shows 1 stable version even though, there are more available. I suppose that happens, because the graphs only look into stable package releases returned by the first page.
An API endpoint returning only stable versions across multiple pages, would make packages like that a lot easier to compare.
Additional information
- Would you be willing to help implement this feature?
Final checks
- Read the contribution guide.
- Check existing issues.
Activity
anilloutombam commentedon Aug 4, 2026
I can take this one.
The issue seems to be that pagination happens before prereleases are filtered out. For packages with a lot of beta/canary releases, the first page may contain very few stable versions.
I’m planning to move the stable-version filtering into the timeline API so it happens before pagination. I’ll make the corresponding change to the install-size endpoint to keep both datasets aligned, update the cache keys, and add coverage for packages with a large number of prereleases.
Since the API already works with the complete version list, this shouldn’t add any extra registry requests.
Let me know if that approach works for you.