Update split chunk handling for edge/node (#62205)
While investigating OOMs noticed that our split chunks handling for edge runtime isn't optimized properly causing a lot of duplicate transpiling/minification which causes exponential memory/cache usage. On a minimal app before this change the memory usage and cache size were over `2GB`s after this change they are under `200MB`. **Before**  **After**  Closes NEXT-2521
Showing
Please
register
or
sign in
to comment