css-in-js
inline-style-prefixer
Our great sponsors
| css-in-js | inline-style-prefixer | |
|---|---|---|
| 3 | - | |
| 5,532 | 392 | |
| - | - | |
| 0.0 | 0.0 | |
| about 3 years ago | over 1 year ago | |
| JavaScript | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
css-in-js
-
Front-end Guide
As you might have realized by now, the front end ecosystem is saturated with tools, and unsurprisingly, tools have been invented to partially solve some of the problems with writing CSS at scale. "At scale" means that many developers are working on the same large project and touching the same stylesheets. There is no community-agreed approach on writing CSS in JS at the moment, and we are hoping that one day a winner would emerge, just like Redux did, among all the Flux implementations. For now, we are banking on CSS Modules. CSS modules is an improvement over existing CSS that aims to fix the problem of global namespace in CSS; it enables you to write styles that are local by default and encapsulated to your component. This feature is achieved via tooling. With CSS modules, large teams can write modular and reusable CSS without fear of conflict or overriding other parts of the app. However, at the end of the day, CSS modules are still being compiled into normal globally-namespaced CSS that browsers recognize, and it is still important to learn and understand how raw CSS works.
-
Why are "CSS classes generally better for performance than inline styles." ~ from react docs
There are a myriad of CSS-in-JS tools, many of which are zero-runtime giving you all the benefits of authoring in a single file without the drawbacks of inline styles. That's how I prefer to do my CSS with React anyway... Vanilla Extract and/or Linaria are my current favorites.
-
Why was CSS-In-JS ever a thing?
One thing I think you're really missing is what the output is of CSS-in-JS. There are tens of CSS-in-JS frameworks that can output anything from: CSS Module like classes (Linaria, Vanilla Extract), Atomic Classes (StyleX, PreStyle), to the more traditional (Styled Components, Emotion) many with zero runtime cost (ie no JS bloat). That's why I say CSS-in-JS is primarily about developer experience... the output can often be whatever you want it to be.
inline-style-prefixer
We haven't tracked posts mentioning inline-style-prefixer yet.
Tracking mentions began in Dec 2020.
What are some alternatives?
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript
react-responsive - CSS media queries in react - for responsive design, and more.
crisp-react - React boilerplate written in TypeScript with a variety of Jamstack and full stack deployments. Comes with SSR and without need to learn a framework. Helps to split a monolithic React app into multiple SPAs and avoid vendor lock-in.
Radium - A toolchain for React component styling.
linaria - Zero-runtime CSS in JS library
postcss-js - PostCSS for React Inline Styles, Free Style and other CSS-in-JS
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
ESLint - Find and fix problems in your JavaScript code.
classnames - A simple javascript utility for conditionally joining classNames together
Rollup - Next-generation ES module bundler
react-container-query - :package: Modular responsive component