With the checkin of #10362, the code to render to a stream now looks like:

```
import { renderToStream } from 'react-dom/server'

renderToStream(<div>some text</div>).pipe(response);
```

This is great! I am, however, a little concerned about taking the word "node" out of the mix, because I'm thinking that we may eventually want to render to [**browser** streams](https://www.w3.org/TR/streams-api/), which are a really neat feature that can be used in concert with "service-worker-side rendering". I would propose renaming `renderToStream` to `renderToNodeStream` and `renderToStaticStream` to `renderToStaticNodeStream`.  This would give room for `renderToBrowserStream` in the future.

If I make a PR on this, would it have a chance of being accepted? 

cc @gaearon & @sebmarkbage 
return {value: <div key={i} />, done: false};
                } else {
                  return {value: undefined, done: true};
                }
              },
            };
          },
        };
        let e = await render(threeDivIterable);
        let parent = e.parentNode;
        expect(parent.childNodes.length).toBe(3);
        expect(parent.childNodes[0].tagName).toBe('DIV');
        expect(parent.childNodes[1].tagName).toBe('DIV');
        expect(parent.childNodes[2].tagName).toBe('DIV');
      });
      itRenders('emptyish values', async render => {
        let e = await render(0);
        expect(e.nodeType).toBe(TEXT_NODE_TYPE);
        expect(e.nodeValue).toMatch('0');
        
        
        expect((await render(<div>{''}</div>)).textContent).toBe('');
        expect(await render([])).toBe(null);
        expect(await render(false)).toBe(null);
        expect(await render(true)).toBe(null);
        expect(await render(undefined)).toBe(null);
        expect(await render([[[false]], undefined])).toBe(null);
      });
    }
  });