60dd6dfc9b
## Bug The `findDOMNode` will be exported from ReactDOM in esm mode, but it's not defined for SSR since SSR is using react-dom server stub bundle which doesn't contain any thing. So `import { findDOMNode } from 'react-dom'` will error in that case with bundling. Since it's only being used on client, we import ReactDOM and call `ReactDOM.findDOMNode` to avoid bundling error and adding a condition to tree-shake it off on client [slack thread](https://vercel.slack.com/archives/C03KAR5DCKC/p1670608621289259) - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) |
||
---|---|---|
.. | ||
react-dev-overlay | ||
app-router-headers.ts | ||
app-router.tsx | ||
bailout-to-client-rendering.ts | ||
error-boundary.tsx | ||
error.tsx | ||
head.tsx | ||
headers.ts | ||
hooks-server-context.ts | ||
infinite-promise.ts | ||
layout-router.tsx | ||
match-segments.ts | ||
navigation.ts | ||
noop-head.tsx | ||
not-found.ts | ||
redirect.ts | ||
reducer.ts | ||
render-from-template-context.tsx | ||
request-async-storage.ts | ||
static-generation-async-storage.ts | ||
static-generation-bailout.ts | ||
use-reducer-with-devtools.ts |