7d93808c43
Currently we create separate workers to isolate `pages` and `app` routers due to differing react versions being used between the two. This adds overhead and complexity in the rendering process which we can avoid by leveraging an `esm-loader` similar to our `require-hook` to properly alias `pages` router to the bundled react version to match `app` router when both are leveraged together. This aims to seamlessly inject the `esm-loader` by restarting the process with the loader arg added whenever `next` is imported so that this also works with custom-servers and fixes the issue with custom req/res fields not working after upgrading. x-ref: https://github.com/vercel/next.js/issues/53883 x-ref: https://github.com/vercel/next.js/issues/54288 x-ref: https://github.com/vercel/next.js/issues/54129 x-ref: https://github.com/vercel/next.js/issues/54435 closes: https://github.com/vercel/next.js/issues/54440 closes: https://github.com/vercel/next.js/issues/52702 x-ref: [slack thread](https://vercel.slack.com/archives/C03KAR5DCKC/p1693348443932499?thread_ts=1693275196.347509&cid=C03KAR5DCKC) --------- Co-authored-by: Tim Neutkens <tim@timneutkens.nl> Co-authored-by: Zack Tanner <zacktanner@gmail.com> Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| pages | ||
| test | ||