Bug: Browser builds of `/static` and `/server` hang indefinitely in Node upon completion in v19

[rschristian]

When running in Node, renderToString (along with all other rendering methods, from my tests) from react-dom/server.browser and prerender from react-dom/static.browser seem to hang indefinitely -- the actual rendering completes just fine but the Node process is completely stuck afterwards and will not exit. This was not the case in v18, server.browser worked just fine in Node there.

React version: 19.1.0

Steps To Reproduce

// index.js
import { jsx } from 'react/jsx-runtime';
import { renderToString } from 'react-dom/server.browser';

const App = () => jsx("h1", { children: "Hello World!" });

const content = renderToString(jsx(App, {}));

console.log(content); // Prints `<h1>Hello World!</h1>` as expected, no issue here

1. $ node ./index.js

Code example: https://stackblitz.com/edit/node-6nxmucbr?file=index.js

The current behavior

Hangs indefinitely, process will not exit once prerendering has completed

The expected behavior

Process should exit once prerendering has completed

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[rschristian]

Still an issue unfortunately.

[darhsu]

I can confirm that I am running into this issue too

[eps1lon]

Why are you not using react-dom/server or react-dom/server.node in Node.js?

[rschristian]

Portability, essentially, as I need to run in multiple envs and having a special bundle for Node is quite silly when the "browser" (standards-based) build should suffice.

[eps1lon]

You should use the .edge build in this case. Using browser in Node.js makes no sense since the Browser has APIs that Node.js doesn't have. Timing heuristics may also differ so it's generally unsafe. react-dom/server.edge uses a subset that both environments support.

[rschristian]

For basic renderToString? What APIs could you possibly need?

As I state above, it does function correctly, the process just hangs afterwards. Unfortunately I am stuck with the browser build though it's good to know about .edge.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!