- fix(turbopack): Do not create invalid `EcmascriptModulePartAsset` by kdy1 · Pull Request #70016 · vercel/next.js
- What? EcmascriptModulePartAsset is invalid if the splitting is failed. We now carefully create it, only when the original module is splitable. Why? This is part of the tree-shaking PR. How?
It was a very minor change, logically perfect, yet it broke the test case. The problem was that the cause was completely unclear...
So, even though it was my birthday weekend, I had to do some grunt work. I applied the old logic to some files based on their filenames to figure out which files were incompatible with the new logic.
I did this grunt work one by one like this,
and finally figured out the problematic test case. But the contents of that file were
all. Since it seemed like debugging would take a long time, I deactivated the related test case.
Comments0