Great question — answering as the UphillTech team:
About your ChunkLoadError From what you described, I don’t think the main problem is that the chunk doesn’t exist. The suspicious part is the combination of deployments, caching, and the custom splitChunks configuration. The browser can receive HTML/RSC from one deployment and later try to load a chunk belonging to another deployment. The fact that the file exists in the current deployment doesn’t necessarily mean it belongs to the same deployment that generated the HTML the user received. That would also explain why this only affects a small percentage of users. What I would change first I would remove the custom splitChunks configuration temporarily and let Next.js handle chunking itself:...
Full answer by dnetto: https://stackoverflow.stackexchange.com/a/80004855 (CC BY-SA 4.0).
Need it done for your business? UphillTech.
