Updating to Nextjs 16 and enabling cacheComponents

[RubenZx]

Summary

Hello!

I have a large Next.js project currently on v15.5.6 and a branch that updates it to v16.0.4. In v16.0.4, when cacheComponents is disabled, the project deploys to Vercel without issues.

After enabling cacheComponents, I removed deprecated features (dynamicParams, revalidate, etc) and added the required Suspense boundaries. The project builds and runs successfully locally, but Vercel fails during the build with a SIGKILL OOM error.

Next, I tried adding caching to one of my pages that generates around 1527 static paths, using use cache in my fetch helper. With this change, the Vercel build progresses further, but eventually got stuck with RangeError: Invalid string length. It seems like enabling component caching significantly increases memory usage or the size of the serialized data at build time.

Is there something extra I need to configure after enabling cacheComponents in order to deploy successfully to Vercel?

Additional information

No response

Example

No response

[icyJoseph]

This is good input. I wonder if you can try to take it through the support so that we can take a look at the project? I also wonder if the cache key is somehow getting out hand in this instance? It'd be nice if we could debug a bit more. Are you able to build locally though?

[bgw]

Internal issue for tracking the support ticket: https://linear.app/vercel/issue/NEXT-4804/