Drupal returning 2000 paths per request maximum

[ysvahn]

Hi, I found something quite odd when building an app with more than 2000 paths.

I have 6000 (3000 x 2 languages) nodes of one type (artwork) in my Drupal database but when I'm building the app, only 2000 are actually built when building the pages under /artworks/[...slug].js.

Is this a limitation from next-drupal, the next Drupal module or even the subrequests module ? I know that the basic Drupal/JSONAPI is limited to 50 nodes per request but I believe subrequests go through.

If we can't bypass this limitation, are we able to use limits to queue requests as long as we do not have all nodes ?

[shadcn]

You're probably hitting the 1000 max size that the Next.js module sets.

See

next-drupal/modules/next/modules/next_jsonapi/next_jsonapi.services.yml

Line 1 in db2f99c

parameters:

Can you try overriding this parameter in your sites services.yml file?

[ysvahn]

It seems to be working but I am hitting the 60 seconds timeout when retrieving the nodes now, so the build does not even start, do you know where I can change the timeout value ?

[ysvahn]

OK, there is an experimental flag to add in next.config.js :
experimental.pageDataCollectionTimeout is 60 by default, problem solved !

I will have to create a patch on the .yml file to make sure that the value never changes :)

[shadcn]

I will have to create a patch on the .yml file to make sure that the value never changes :)

Do you mean the next_jsonapi.size_max value?

You could also look into ISR and only build the most important pages and let the other pages be server rendered.