Material-UI v4 display warnings when used with next-with-apollo

[ralvs]

Related issue at MUI repository: #15798

After update to Material-UI v4.0, lots of warnings started to show at DevTools.
If I remove next-with-apollo and follow the example with-apollo-auth, everything works fine.

[eps1lon]

Issue is likely caused by bundling a polyfill which relies on the window object. window should be undefined on the server IMO.

[oliviertassinari]

I believe we have identified the source of the problem:
mui/material-ui#15798 (comment)

[ivawzh]

Also after I set withApollo(..., { getDataFromTree: 'never' }) and new ApolloClient({ ssrMode: false, ... }), the warnings still persist.

[oliviertassinari]

@ivawzh I have experienced the opposite. It solves the warning in the reproduction provided on Material-UI side.

[ghost]

Im experiencing the same as here, setting withApollo(..., { getDataFromTree: 'never' }) has no impact on the warnings.
Following the next repository example does not exhibit this error. Ill continue to dig into the differences, but there is an incompatibility between this library and material-ui currently.

Update: @oliviertassinari solution did actually work for me in the end - which makes sense because the example wraps getDataFromTree in a SSR only test whereas this library defaults to client and server.
You have to be very careful where you place the option value. I had it in the wrong place.

@lfades would it make more sense to default getDataFromTree as SSR only? Since the client instance is reused - im not sure why its defaulted to always.

[nicovalencia]

Make sure you're getting what you're expecting from the re-render, but if you're looking for the happy path SSR hydration, this should work:

export default withApollo(createClient, { getDataFromTree: 'ssr' });

[wesbos]

This can be closed

[vitaliemiron]

now withApollo function have another interface, can you post please new example how to fix this?