Next Build Hangs When Static Generation Worker Batch Exceeds V8 Max String Length

In Next.js 16.4.0-canary.58, the static generation worker sends the complete batch result to the parent via a single process.send() IPC message. With cacheComponents, each page includes serialized resume data cache, making the aggregate serialized payload exceed V8's maximum string length (~536,870,888 characters). The resulting RangeError from process.send is not caught, triggering an unhandledRejection in the worker, and the parent never receives a result or error, causing a permanent hang. Underlying design flaw: IPC result transfer lacks chunking, streaming, or size validation.

1. Clone the reproduction repository: https://github.com/AdzerKI/next-export-batch-ipc-limit 2. Run `npm ci` 3. Run `npm run build` 4. Observe build hangs indefinitely at 'Generating static pages' (expected finish or explicit error).

This fix causes the build to fail instead of hang; it does not allow successful builds with large cacheComponents batch sizes. For production-scale static exports with heavy resume data, a more comprehensive solution involving chunked IPC or streaming is required. Rollback guidance: if this patch causes unexpected behavior, revert to the original process.send call and temporarily disable cacheComponents or reduce the number of pages per worker batch. In concurrent or multi-threaded builds, multiple workers may send error messages simultaneously; the parent must handle error events idempotently. If a future Next.js release introduces official chunking, this patch may conflict and should be removed.