Sebastian "Sebbie" Silbermann

> Needs a rebase because the commit from https://github.com/vercel/next.js/pull/71423 is included here as well. If you merge stacked PRs via Graphite this usually works better. Yeah, but Graphite waits for...

* **#71909** 👈 (View in Graphite) * **#73439** * **#73420** * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking.

* **#71718** * **#71717** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates on Graphite

### Merge activity * **Oct 23, 4:40 PM GMT+2**: A user merged this pull request with [Graphite](https://app.graphite.dev/github/pr/vercel/next.js/71717).

* **#71821** * **#71820** * **#71803** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates...

* **#67422** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @eps1lon and the rest of your teammates on Graphite

Can you reproduce this with a production build as well? We have a similar issue that only happens in dev with `StrictMode`: https://github.com/facebook/react/issues/32561

> new next 14 apps will actually install a very old canary eslint-plugin-react-hooks@5 from July 2023 as I mentioned before, instead of 4.6.2. And that's a regression, if you ask...

Which Node.js version are you using? Different versions of Node.js could change the snapshots.

It's not an optimization but a bug fix. mdx-bundler currently bundles the jsx-runtime which isn't supported (it's like bundling React itself). This worked because all supported versions of React were...