The insights page returns a blank page

[teolemon]

What

https://hunger.openfoodfacts.org/insights

Log

Success: https://hunger.openfoodfacts.org/
index-Bw4VOUSr.js:5 Uncaught TypeError: n.call(...).some is not a function
at index-Bw4VOUSr.js:5:12188
at iv (index-Cm4lwofO.js:49:48581)
at Xw (index-Cm4lwofO.js:49:68144)
at uS (index-Cm4lwofO.js:49:83853)
at FS (index-Cm4lwofO.js:49:117698)
at Dz (index-Cm4lwofO.js:49:116738)
at Wv (index-Cm4lwofO.js:49:116568)
at PS (index-Cm4lwofO.js:49:113341)
at JS (index-Cm4lwofO.js:49:125221)
at MessagePort.Z (index-Cm4lwofO.js:26:1596)
(anonymous) @ index-Bw4VOUSr.js:5
iv @ index-Cm4lwofO.js:49
Xw @ index-Cm4lwofO.js:49
uS @ index-Cm4lwofO.js:49
FS @ index-Cm4lwofO.js:49
Dz @ index-Cm4lwofO.js:49
Wv @ index-Cm4lwofO.js:49
PS @ index-Cm4lwofO.js:49
JS @ index-Cm4lwofO.js:49
Z @ index-Cm4lwofO.js:26Understand this error

[Adithyasy105]

Hi!

I looked into this issue and tested the Insights page locally.
The blank screen was happening due to incorrect pagination state handling in the DataGrid, causing the pagination component to break and blocking the fetch for the next page.

I implemented a fix that is:

• Correctly syncs pageSize with the DataGrid pagination model
• Ensures onPaginationModelChange fetches the correct rows for each page
• Removes the type error related to invalid pagination state
• Restores the Insights feed so new rows load properly when navigating pages

I have a working patch ready and tested locally

One question:
On mobile view, the page-size selector (Rows per page) does not appear — only the default 25 rows are shown.
Is this expected behavior on mobile or should we expose the selector there as well?

If this approach looks good, may I submit a PR for it and get assigned to this issue?
Happy to update or refine anything as needed!

[alexfauquette]

On mobile view, the page-size selector (Rows per page) does not appear — only the default 25 rows are shown.
Is this expected behavior on mobile or should we expose the selector there as well?

Yes, don't worry too much about mobile, this page is mostly used by desktop power users

If this approach looks good, may I submit a PR for it and get assigned to this issue?

Yes feel free to open PR