docs: reference stylex and pandacss in css-in-js
This commit is contained in:
committed by
Stefan Rotsch
parent
3081ef0d6d
commit
c7f55c2d01
@@ -9,7 +9,7 @@ Since the release of React 18, many CSS-in-JS libraries like styled-components,
|
|||||||
|
|
||||||
This has created substantial uncertainty among developers and the communities of these affected libraries. The question arises: Is it possible to refactor these runtime libraries into buildtime libraries? To date, none of the libraries have announced any such plans, and, unfortunately, one of the most popular new libraries, stitches, is [no longer being maintained](https://github.com/stitchesjs/stitches/discussions/1149#discussioncomment-6223090).
|
This has created substantial uncertainty among developers and the communities of these affected libraries. The question arises: Is it possible to refactor these runtime libraries into buildtime libraries? To date, none of the libraries have announced any such plans, and, unfortunately, one of the most popular new libraries, stitches, is [no longer being maintained](https://github.com/stitchesjs/stitches/discussions/1149#discussioncomment-6223090).
|
||||||
|
|
||||||
Fortunately, there has been a growing number of CSS-in-JS solutions that generate CSS at buildtime. Libraries like [Vanilla Extract](https://vanilla-extract.style/), [panda](https://panda-css.com/), and [Kuma UI](https://www.kuma-ui.com/) maintain an excellent developer experience, overcome performance disadvantages, and are compatible with React 18.
|
Fortunately, there has been a growing number of CSS-in-JS solutions that generate CSS at buildtime. Libraries like [Vanilla Extract](https://vanilla-extract.style/), [Panda CSS](https://panda-css.com/), and [Kuma UI](https://www.kuma-ui.com/) maintain an excellent developer experience, overcome performance disadvantages, and are compatible with React 18.
|
||||||
|
|
||||||
Unfortunately, these libraries are not yet widely adopted, and it's challenging to predict how they will develop in the future. Therefore, at AOE, we continue to use established solutions as long as the new React features are not mandatory.
|
Unfortunately, these libraries are not yet widely adopted, and it's challenging to predict how they will develop in the future. Therefore, at AOE, we continue to use established solutions as long as the new React features are not mandatory.
|
||||||
|
|
||||||
|
|||||||
8
radar/2024-06-01/css-in-js.md
Normal file
8
radar/2024-06-01/css-in-js.md
Normal file
@@ -0,0 +1,8 @@
|
|||||||
|
---
|
||||||
|
title: "CSS-in-JS"
|
||||||
|
ring: adopt
|
||||||
|
quadrant: methods-and-patterns
|
||||||
|
tags: [coding, frontend]
|
||||||
|
---
|
||||||
|
|
||||||
|
Since the last release, [Stylex](/languages-and-frameworks/stylex/) and [Panda CSS](/languages-and-frameworks/panda-css/) have emerged as the most promising CSS-in-JS solutions for us.
|
||||||
Reference in New Issue
Block a user