Find out how to sample React Aria Elements with TailwindCSS

React Aria Elements (RAC) is a library from Adobe that will provide you with fully available and production-ready React components, again without any pre-defined styling. This makes RAC the best possible for pairing with a styling framework like TailwindCSS, because you’ll be able to design the entire project exactly the way you want without having to fight for preset types.

I use RAC in a relatively large number of tasks, and one thing I like about RAC is the way it handles phase states. As a replacement for simply using CSS pseudo-classes like :hover OR :vigorous which don’t always perform repeatedly on the touch gadgets or keyboards he uses data- attributes such as data-hovered, data-pressedAND data-selected.

Using with TailwindCSS

TailwindCSS is one of my favorite ways to style components. While React Aria Components graphics are simply smart with TailwindCSS, there is a problem when it comes to styling phase states. Since RAC uses data attributes, you will have the option to not just use the same old ones as Tailwind hover: OR focus: variations. Instead, you want to write the entire functionality using Tailwind’s arbitrary variant syntax, for example:

This works beautifully, but can be redundant. In short, class names can become long and confusing, which makes our code harder to read and scan. Additionally, we lose the Tailwind editor’s handy autocomplete, so typos most likely become much more likely.

This is exactly the problem that the tailwindcss-react-aria-components plugin is designed to solve. Let’s see how it works.

Organize

Plugin configuration is underrated. We can add it with NPM with this command below:

npm arrange tailwindcss-react-aria-components

The plugin configuration depends on the type of Tailwind you are using to solve the problem.

On Tailwind v3add it to yours tailwind.config.js:

/** @type {import('tailwindcss').Config} */
module.exports = {
  //...
  plugins: [
    require('tailwindcss-react-aria-components')
  ],
}

On Tailwind v4use the new one @plugin directive on your number one CSS record:

@import "tailwindcss";
@plugin "tailwindcss-react-aria-components";

Once installed, the styling phase is further simplified. Detailed data attributes such as data-[pressed]: grow to be clean variants very similar to pressed:AND data-[selected]: becomes selected:. Non-Boolean states, for example, are also shorter data-orientation="vertical" now it becomes orientation-vertical:.

That’s right, here’s a quick comparison between the two approaches for one of the vital states in RAC:

RAC status	Tailwind function selector	Simplified class selector
isHovered	data-[hovered]	hovered:
isPressed	data-[pressed]	pressed:
isSelected	data-[selected]	selected:
isDisabled	data-[disabled]	disabled:
isFocusVisible	data-[focus-visible]	focus-visible:
isPending	data-[pending]	pending:

Prefix

By default, plugin modifiers are not pre-fixed, so you will have the option to use variations like disabled: immediately, for example:

import { Button } from 'react-aria-components';

function App() {
    return (
        
            Put up
        
    );
}

On the other hand, even if you need a clearer naming convention, you will have the option to set a prefix throughout the configuration. This can also be particularly useful in higher-level tasks where you want to avoid conflicts with other plugins or custom-designed utilities.

Again, the setup depends on the type of Tailwind you’re using.

On Tailwind v3you will have the option to add the prefix option when you request the plugin to be installed tailwind.config.js:

// tailwind.config.js
/** @type {import('tailwindcss').Config} */
module.exports = {
  //...
  plugins: [
    require('tailwindcss-react-aria-components')({ prefix: 'rac' })
  ],
}

On Tailwind v4you will have the option to move the prefix possibility throughout the file @plugin directive on your number one CSS record, as below:

@import "tailwindcss";
@plugin "tailwindcss-react-aria-components" { prefix: hk };

It is now also possible to prefix all variants rac-AS disabled: becomes rac-disabled:AND selected: becomes rac-selected:.

That’s right, here’s the same example as before, then again with the prefix applied:

import { Button } from 'react-aria-components';

function App() {
    return (
        
            Put up
        
    );
}

Here is a short demo of the plugin in action.

In conclusion

Styling React Aria components with TailwindCSS doesn’t have to be difficult. With the tailwindcss-react-aria-components plugin, you’ll have the ability to skip the detailed syntax and graphics with clean, intuitive variations that look really similar to Tailwind’s native utilities. This makes it much easier to keep the code readable, the workflow empty, and the components available using the default.

In this article we got excited about styling. After all, this is only the beginning. In the next one, we’ll take it a step further and find out how to animate React Aria components with TailwindCSS, along with hollow motion to make your UI much more refined and attractive.

Stay tuned!

The publication Learn How to Taste React Aria Elements with TailwindCSS first made an impression on Hongkiat.

wordpress website development

Scope of delivery: https://www.hongkiat.com/blog/react-aria-tailwindcss-styling/

[ continue ]

wordpress Maintenance Plans | wordpress hosting

Read more