Expected to render css on the server first, using specific code in _document.js. So, expected behavior would be to see no FOUC.
CSS is not rendered on the server, only on the client. It's interesting that class names are applied correctly on the server, only actual CSS is not rendered. As the result, we see FOUC before client side catch up.
This happened right after updated to 5.0. Latest canary releases also broken.
curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/with-felacd with-felayarnyarn dev| Tech | Version |
|---------|---------|
| next | 5.0.0 / 5.0.1-canary.4 / 5.0.1-canary.5 / 5.0.1-canary.9 |
| node | 9.5.0 |
| OS | OSX 10.13.3 |
same issue here , any luck with this?
Tech | Version
-- | --
next | 5.0.0
node | 8.9.1
OS | OSX 10.13.2
@danielantelo Not much so far. Had to downgrade next to 4.4 for now :(
I also struggle with that and am using Next 4.4 for now. Seems to be the same for Styletron, Aphrodite and all the other solutions that use the getInitialProps method to cluster CSS.
Any update on this? Weuse Fela and are building an app that needs the zones feature in 5
This issue needs more attention, any ETA?
@ilionic I agree, this one is really critical.
ETA: today.
As I need this to work for myself, I hacked around till I got it working.
Will update the example asap.
Most helpful comment
ETA: today.
As I need this to work for myself, I hacked around till I got it working.
Will update the example asap.