Our great sponsors
-
I tried Nextjs 13 today, with the new app directory that uses server component by default. I tried using mantine.dev in this project (which uses emotion/core). This will throw an error of ou're importing a component that needs flushSync. It only works in a Client Component. I wonder if the problem lies with emotion/core's SSR strategy or if it's just we should use only style libraries like tailwind for server components.
-
Anything that uses css-in-js (styled-components / emotion) won't currently work properly: https://beta.nextjs.org/docs/styling/css-in-js the problem isn't related to emotions SSR strategy as that relates to client components being statically pre-rendered. The problem actually relates to the implementation of these solutions as they do not work very well with the new concurrent rendering patterns of react 18 and they haven't completed the upgrade process explained here: https://github.com/reactwg/react-18/discussions/110 this will be a pretty large fundamental change to emotion, so may take a fair while to fully support it, especially given that next's app folder is still a beta feature :)
-
Klotho
AWS Cloud-aware infrastructure-from-code toolbox [NEW]. Build cloud backends with Infrastructure-from-Code (IfC), a revolutionary technique for generating and updating cloud infrastructure. Try IfC with AWS and Klotho now (Now open-source)
-
Try react daisy ui which is tailwind based.