Technology Spotlight: Chakra UI

Ryan Padilla
November 17th 2020


Chakra UI is an up and coming library of React components that is super easy to use, while also taking care of accessibility for you. They’re very easy to compose and style, and I feel that my code has become cleaner and more modular as a result. The defaults for components are reasonable and provide flexibility out of the box, while allowing for more specific styling through emotion.js if you can’t get what you need through the styled props API. At the time of writing, they are still working on release candidates for version 1.0, but the stable release of 0.8 has worked quite well, if not for a couple typescript quirks. Chakra offers much out of the box functionality, so I won’t attempt to mention everything, but I can at least give insight what I’ve enjoyed about it in the context of a client project.

Color Theming

I’ve absolutely loved the way chakra encourages color themes. By creating a color palette of 10 shades around a color, Chakra components can automatically create states for hover, active, disabled, etc.
Someone forgot to caption me
After you’ve defined your color palette, by passing the variantColor prop to supported components, you’re all set!
<Button variantColor="green">Button</Button>

Simplifying Inline Styling with Style Props

Chakra UI uses Styled System to offer a way to alter the style of a component by passing props to it. This also provides shorthand versions of common props, like margin as “m” and padding as “p”. Drawing from the constraint based design system, it's possible to pass an array of variables so your theme-defined breakpoints can determine which value to use. If you’re curious about how this works, check out this page. Great typescript integration also allows for tab completion of certain style props. For small differences between components, inline styling is such a breeze:
<Text {...bodyMedium} textTransform="uppercase" fontWeight={400} m=”4px”>
  Hello there!
Coming from a Styled Components approach where all your styled divs, buttons, etc for a single file are defined at the top, this took some getting used to. But I quickly realized how much easier it is for me to change styles without needing to context switch to a different part of the file, and also to figure out when I needed to refactor something into a base component. When the component begins to grow in style complexity, and thus code length, naturally you’ll want to move it to its own file. Which leads me to my next point…

Ease of Composability

Since the library is built on typescript, not only are the components typed, but the prop types are exported as well. This makes it very simple and easy to do something like this:
export interface CommonButtonProps extends ButtonProps {
  buttonStyle?: 'large' | 'small' | 'strong';
This gives you the great flexibility of being able to use your base components, in my case large, small, or strong buttons, while still being able to pass along Chakra button props without hassle.

Large Selection of Pre-built Components

Rather than having to port your pre-built code from other projects for things like modals and drawers, nearly everything you need is pre-built and accessible, you need only to style it if you want. I gotta hand it to the Chakra team, they did a great job making the component re-styling pretty hassle free.

Emotion styling when needed

When you do need to get a bit more specific, you can do the following:
Import jsx from emotion, css and useTheme from Chakra
/** @jsx jsx*/
// @ts-ignore (needed since typescript complains jsx is not used)
import { jsx } from '@emotion/core';
Inside your component, create your specific styles
const theme = useTheme();
const styles = css({
   '&:hover': {
      path: {
      fill: 'white',
  '&[data-active]': {
    path: {
      fill: 'white',
Then, in your component, attach the styles variable to the css prop:
<Button {...props} css={styles}/>
In my case, I had to do some specific styling to child path components of an svg, since the isActive boolean property added the data-active property, and doesn't trigger the native browser active event.


After the slight adjustment coming from “styled components”, I think Chakra UI is going to be my preferred method for component implementation in the future. That’s not to say “styled components” is bad, just that the ease of use and general paradigm that Chakra presents is more appealing to me. Looking forward to the release of version 1.0!

Want invites to cool events and things?

Boom, Newsletter sign up form.