Caching issue with Next.js App Router - Vercel Deployment

Developing with Prismic
14

This was helpful. We had a similar situation. When there is multiple [:uid]/page.js files, e.g. /[:uid]/page.js and /some-path/[:uid]/page.js

It seems like subsequent createClient() calls trigger a not-found repo error. There very well be some kind of fetch cache on createClient() or client.getAllByType(...).

After adding Kyle's suggestion:

  • client.getByType('page')
  • client.getAllByType('page')
  • as well as creating a static array of uid's

All work as expected within generateStaticParams()

It probably stems from the changes in fetch with next.js 13.x and the app router. All fetch requests get cached by default (it think).

1 Like