-
Notifications
You must be signed in to change notification settings - Fork 28k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Started Docs: CSS #73341
Getting Started Docs: CSS #73341
Conversation
All broken links are now fixed, thank you! |
Co-authored-by: Rich Haines <hello@richardhaines.dev>
@leerob I'll apply the feedback above in a new PR since this one relates to CSS. |
- [`stylex`](https://stylexjs.com) | ||
- [`tamagui`](https://tamagui.dev/docs/guides/next-js#server-components) | ||
- [`tss-react`](https://tss-react.dev/) | ||
- [`vanilla-extract`](https://vanilla-extract.style) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi there! We are using vanilla-extract in Server Components since quite some time, so I not sure the warning that it only works in Client Components is accurate. vanilla-extract uses a plugin that generates static CSS and className
s just like CSS Modules (but uses TypeScript for generating the stylesheet), what would not work in Server Components?
Please merge this PR first: #73340
Closes: https://linear.app/vercel/issue/DOC-3698/page-css-styling