MrOxMasTer

> It's frustrating to have to keep declaring **'use client'.** The thing is, we're waiting for someone to innovate with a CSS-in-JS solution that handles **SSR**. I believe some libraries...

> I also used styled-components, but when server components have come it became not so smooth in terms of DX. I had a UI library and everywhere where I create...

> I also used styled-components, but when server components have come it became not so smooth in terms of DX. I had a UI library and everywhere where I create...

> > Server rendering is minimal because yes, SC uses a context that does not support server rendering > > I do not understand it clearly. If you have styled...

> > > Server rendering is minimal because yes, SC uses a context that does not support server rendering > > I do not understand it clearly. If you have...

> If you add 'use client' you still have server side rendering, even for styled components. > > https://nextjs.org/docs/getting-started/react-essentials#the-use-client-directive > > > Components in the Client Component module graph are...

> If you add 'use client' you still have server side rendering, even for styled components. > > https://nextjs.org/docs/getting-started/react-essentials#the-use-client-directive > > > Components in the Client Component module graph are...

> In that terms - yes. Because in case of SSR ('use client') your component is executed twice - first on server and second one on client. Also, everything you...

@Angelelz > Lastly, for the people having problems with migrations and push commands, the `serial` type have some weird behaviors. So it's not drizzle's fault. [Check here](https://stackoverflow.com/questions/9490014/adding-serial-to-existing-column-in-postgres) if you want...

> The issue here was about types in the ORM. Kit problems were not being tracked in this issue. We try to assign `drizzle-kit` label to drizzle kit issues. Okay,...