Our great sponsors
-
The differentiating feature of Atlassian’s @compiled package is not the “build time atomic css” - it’s that you can distribute components that use @compiled on NPM without requiring your consumer to futz with Webpack include paths for e.g. CSS files. Do I have that right? @madou is the extraction shipping yet? The docs have a few places that say “coming in 2021” - what’s the status?
If all you’re interested in is build-time CSS in JS, also called Zero-runtime CSS in JS, you might also be interested in:
- Linaria (https://github.com/callstack/linaria) I use on my personal site. I ran into trouble/bugs trying to integrate it with Notion’s build process.
- Treat requires that you write the JS that computes your styles in esperare xxx.treat.js files which is annoying from my point of view - I want single file components. (https://seek-oss.github.io/treat/)
- No idea about this one, but it’s more recent https://github.com/CraigCav/css-zero
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Works with any framework or with none, apparently, although I've only used it with Preact. Supports themes. Everything I need and nothing I don't.
Related posts
- How we improved page load speed for Next.js ecommerce website by 1.5 times
- How bad is it to use CSS-in-JS with regards to the future of React?
- JSS vs Styled Components? and why?
- What is the best CSS framework to use with React? why?
- Why TBT (Script Evaluation) is a bottleneck for CSS in JS even when SSR/SSG