Niklas Mischkulnig
Niklas Mischkulnig
> multiple threads That is exactly the reason why we added this atomic write stream in the past. For the distdir, multiple threads writing the same file is probably unwanted....
Can you figure out what the dependency in question is and why it doesn't have it's parent asset? For that rewriting to work, both he `symbol.set` before the if and...
I think this is the same bug as https://github.com/vercel/next.js/issues/86132 If you compare the unit test I added in https://github.com/vercel/next.js/pull/86131 Still not fixed though, unfortunately
* **#80526** 👈 (View in Graphite) * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking.
### Merge activity * **Jun 17, 9:28 AM UTC**: @mischnic merged this pull request with [Graphite](https://app.graphite.dev/github/pr/vercel/next.js/80526).
* **#80527** * **#79459** 👈 (View in Graphite) * **#80625** * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking.
### Merge activity * **Jun 24, 9:33 PM UTC**: @mischnic merged this pull request with [Graphite](https://app.graphite.dev/github/pr/vercel/next.js/79459).
@followbl Any chance you could provide a reproduction? I wasn't aware of any remaining bugs.
You can set `nextConfig.turbopack.moduleIds = "named"` to have the module path instead of that number 647211. But I'm not entirely sure how much that would help
I can reproduce it, but we need a more minimal reproduction. I tried to trim it down by removing imports and reexports while still maintaining the broken prod behehavior, but...