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 
});
  describe('dynamic injection', () => {
    beforeEach(() => {
      
      
      
      
      
      onAfterResetModules = () => {
        const DOMProperty = require('DOMProperty');
        DOMProperty.injection.injectDOMPropertyConfig({
          isCustomAttribute: function(name) {
            return name.indexOf('foo-') === 0;
          },
          Properties: {foobar: null},
        });
      };
      resetModules();
    });
    afterEach(() => {
      onAfterResetModules = null;
    });
    itRenders('injected attributes', async render => {
      const e = await render(<div foobar="simple" foo-xyz="simple" />, 0);
      expect(e.getAttribute('foobar')).toBe('simple');
      expect(e.getAttribute('foo-xyz')).toBe('simple');
    });
  });
});