Github url


by FormidableLabs

FormidableLabs /radium

A toolchain for React component styling.

7.3K Stars 345 Forks Last release: Not found Other 1.1K Commits 61 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Travis StatusAppVeyor StatusCoverage StatusNPM PackageDependency Status gzipped sizeMaintenance Status


yarn add radium # or npm install --save radium

Radium is a set of tools to manage inline styles on React elements. It gives you powerful styling capabilities without CSS.

Inspired by React: CSS in JSby vjeux.

Maintenance Status

Stable: Formidable is not planning to develop any new features for this project. We are still responding to bug reports and security concerns. We are still welcoming PRs for this project, but PRs that include new features should be small and easy to integrate and should not include breaking changes.

For more about what this means for Radium, view our announcement here.


Eliminating CSS in favor of inline styles that are computed on the fly is a powerful approach, providing a number of benefits over traditional CSS:

  • Scoped styles without selectors
  • Avoids specificity conflicts
  • Source order independence
  • Dead code elimination
  • Highly expressive

Despite that, there are some common CSS features and techniques that inline styles don't easily accommodate: media queries, browser states (:hover, :focus, :active) and modifiers (no more .btn-primary!). Radium offers a standard interface and abstractions for dealing with these problems.

When we say expressive, we mean it: math, concatenation, regex, conditionals, functions–JavaScript is at your disposal. Modern web applications demand that the display changes when data changes, and Radium is here to help.

For a short technical explanation, see How does Radium work?.


  • Conceptually simple extension of normal inline styles
  • Browser state styles to support
    , and
  • Media queries
  • Automatic vendor prefixing
  • Keyframes animation helper
  • ES6 class and



Start by wrapping your component class with


, like

export default Radium(Component)

, or

Component = Radium(Component)

, which works with classes,


, and stateless components (functions that take props and return a ReactElement). Then, write a style object as you normally would with inline styles, and add in styles for interactive states and media queries. Pass the style object to your component via


and let Radium do the rest!

<button kind="primary">Radium Button</button>
import Radium from 'radium'; import React from 'react'; import color from 'color'; class Button extends React.Component { static propTypes = { kind: PropTypes.oneOf(['primary', 'warning']).isRequired }; render() { // Radium extends the style attribute to accept an array. It will merge // the styles in order. We use this feature here to apply the primary // or warning styles depending on the value of the `kind` prop. Since its // all just JavaScript, you can use whatever logic you want to decide which // styles are applied (props, state, context, etc). return ( <button style="{[styles.base," styles>
      </button> ); } } Button = Radium(Button); // You can create your style objects dynamically or share them for // every instance of the component. var styles = { base: { color: '#fff', // Adding interactive state couldn't be easier! Add a special key to your // style object (:hover, :focus, :active, or @media) with the additional rules. ':hover': { background: color('#0074d9') .lighten(0.2) .hexString() } }, primary: { background: '#0074D9' }, warning: { background: '#FF4136' } };

Importing Radium

As of


, Radium is built as an ECMAScript Modules-first project. We now have a


entry pointing to our library files with


statements instead of CommonJS


s. We still support CommonJS


s with a special


entry pointing to root


to smooth over this transition. The basic takeaways are:

If you are using ESM with webpack or **``` @std/esm

import Radium from 'radium'; import Radium, {Style} from 'radium';

If you are using **CommonJS** with **Node.js** or **[email protected]** requires work like normal:

const Radium = require('radium'); const {Style} = require('radium');

If you are using **CommonJS** with **[email protected]+**, however, you must instead add


 to the root 


 object import:

const Radium = require('radium').default; // CHANGED: Must add .default const {Style} = require('radium'); // Works as per normal

If you cannot change the


 statements directly (say Radium is included from a different library your project depends on) you can manually tweak the Radium import in your project's webpack configuration with the following:

resolve: { alias: { radium: require.resolve('radium/index'); } }

which will allow

const Radium = require('radium');

 to still work. The configuration effectively forces webpack to point to code from 


 (which points to 


) instead of what is in 



_Note:_ Radium uses


 which is not supported in IE11. You will need to bring in a polyfill like [CoreJs]( in order to support \<IE11.
## Examples

To see the universal examples:

npm install npm run universal

To see local client-side only examples in action, do this:

npm install npm run examples

## How does Radium work?

Following is a short technical explanation of Radium's inner workings:

- Wrap the 


- Recurse into the result of the original 


- For each element:
  - Add handlers to props if interactive styles are specified, e.g. 




, wrapping existing handlers if necessary
  - If any of the handlers are triggered, e.g. by hovering, Radium calls 


 to update a Radium-specific field on the components state object
  - On re-render, resolve any interactive styles that apply, e.g. 


``` , by looking up the element's key or ref in the Radium-specific state

More with Radium

You can find a list of other tools, components, and frameworks to help you build with Radium on our wiki. Contributions welcome!



We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.