Relies on react-dom/server

[jooj123]

I have noticed that this lib relies on react-dom/server being used on client code

Here:

react-lazy/src/lib/wrap.jsx

Line 2 in 889e7af

import { renderToStaticMarkup } from 'react-dom/server'

and here:

react-lazy/src/lib/wrap.jsx

Line 31 in 889e7af

renderToStaticMarkup(React.createElement('noscript', null, children))

Which causes

    at propsWithNoScriptRender (@domain-group_fe-pa-listing-details_0.32.11_2.2.1_client.js:68415)
    at Lazy.render (@domain-group_fe-pa-listing-details_0.32.11_2.2.1_client.js:67848)
    at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (react.js:5941)
    at ReactCompositeComponentWrapper._renderValidatedComponent (react.js:5961)
    at ReactCompositeComponentWrapper.wrapper [as _renderValidatedComponent] (react.js:12353)
    at ReactCompositeComponentWrapper.mountComponent (react.js:5574)
    at ReactCompositeComponentWrapper.wrapper [as mountComponent] (react.js:12353)
    at Object.mountComponent (react.js:12978)
    at ReactCompositeComponentWrapper.mountComponent (react.js:5579)
    at ReactCompositeComponentWrapper.wrapper [as mountComponent] (react.js:12353)

on client code, react-dom/server as far as im aware should not be used on client code

[Merri]

react-dom/server is perfectly valid to be used on client side (they resolved naming confusion by calling it react-dom-server.browser in React 16).

These is currently an issue in React 16 that causes an incorrect warning with noscript elements: facebook/react#10993