As reported in https://github.com/vercel/next.js/issues/56919 it is possible for the ReadableStream controller to be written to after it is already closed. This is because inside an async context a Float method such as `ReactDOM.preload()` can attempt to flush newly created Resources even after the stream has completed.

React version: 

The underlying bug has been in React since Float landed. The expression of the Bug as reported in the Next.js repo was landed in: https://github.com/facebook/react/commit/701ac2e57290f913502c6012c15e815f412f84b7
The first Canary release to have this new expression was: [18.3.0-canary-f81c0f1ed-20230927](https://www.npmjs.com/package/react-dom/v/18.3.0-canary-f81c0f1ed-20230927)


## Steps To Reproduce

1. use `react-dom/server.edge`
2. Ensure the environment supports AsyncLocalStorage
3. Call Float method like `ReactDOM.preload(...)` after an await after the stream has closed

## The current behavior
If the conditions are right the Float call will initiate a write after the stream has closed and there will be a thrown exception

## The expected behavior
The Float call is ignored after the stream has closed. There are no errors
'<html><head></head><body><script>try { foo() } catch (e) {} ;</script></body></html>',
    );
  });
  
  it('warns if script has complex children', async () => {
    function MyScript() {
      return 'bar();';
    }
    const originalConsoleError = console.error;
    const mockError = jest.fn();
    console.error = (...args) => {
      mockError(...args.map(normalizeCodeLocInfo));
    };
    try {
      await act(async () => {
        const {pipe} = renderToPipeableStream(
          <html>
            <body>
              <script>{2}</script>
              <script>
                {[
                  'try { foo() } catch (e) {} ;',
                  'try { bar() } catch (e) {} ;',
                ]}
              </script>
              <script>
                <MyScript />
              </script>
            </body>
          </html>,