Search result pagination displays incorrect page count with empty pages

[MatteoGabriele]

Describe the bug

The number of pages rendered does not match the total number of available pages. Clicking on the last page and subsequent pages reveals that no packages are available for those pages.

Additional context

Screen.Recording.2026-03-04.at.14.19.35.mov

[alex-key]

I've made an investigation, will open a PR soon.

[RevanthPrk]

I have investigated this issue and observed that

When navigating to the 41st page, the entire screen becomes blocked, and none of the functionalities are clickable.

Additionally, when attempting to navigate directly to the last page, we encounter an error stating that the offset value must be between 0 and 1000:
"Value too large for 'length' parameter, expected integer between 0 and 1000."

[alex-key]

This is correct, Algolia has MAX_LIMIT=1000 and npmRegistry MAX_LIMIT=5000

[RevanthPrk]

@alex-key

https://www.algolia.com/doc/api-reference/api-parameters/paginationLimitedTo

I found this and we can also increase the limit to beyond 1000.

But it says that it may impact performance

[alex-key]

@alex-key

https://www.algolia.com/doc/api-reference/api-parameters/paginationLimitedTo

I found this and we can also increase the limit to beyond 1000.

But it says that it may impact performance

👍
Unfortunately search endpoint that we use strictly limited to 1,000. You could check my PR. And I suppose we can't configure it using paginatedLimitedTo as it's a public index available for multiple consumers (jdelivr and others)

[serhalp]

we may have a few related/duplicate issues for this one: #2305 #2020