react-aria
Spectrum UI components in React
About
Spectrum UI components in React
Live mirror of the GitHub README. Updated whenever the repo's default branch changes.
React Spectrum Libraries
A collection of libraries and tools that help you build adaptive, accessible, and robust user experiences.
React Spectrum
A React implementation of Spectrum, Adobe’s design system. Spectrum provides adaptive, accessible, and cohesive experiences for all Adobe applications.
React Aria
A library of unstyled React components and hooks that helps you build accessible, high quality UI components for your application or design system.
React Stately
A library of React Hooks that provides cross-platform state management for your design system.
More information about React Stately
Internationalized
A collection of framework-agnostic internationalization libraries for the web.
Features
- ♿️ Accessible – Accessibility and behavior is implemented according to WAI-ARIA Authoring Practices, including full screen reader and keyboard navigation support. All components have been tested across a wide variety of screen readers and devices to ensure the best experience possible for all users.
- 📱 Adaptive – All components are designed to work with mouse, touch, and keyboard interactions. They’re built with responsive design principles to deliver a great experience, no matter the device.
- 🌍 International – Support over 30 languages is included out of the box, including support for right-to-left languages, date and number formatting, and more.
- 🎨 Customizable – React Spectrum components support custom themes, and automatically adapt for dark mode. For even more customizability, you can build your own components with your own DOM structure and styling using the React Aria and React Stately hooks to provide behavior, accessibility, and interactions.
Getting started
React Spectrum includes several libraries, which you can choose depending on your usecase.
- React Spectrum is an implementation of Adobe's design system. If you’re integrating with Adobe software or would like a complete component library to use in your project, look no further!
- React Aria is a collection of unstyled React components and hooks that helps you build accessible, high quality UI components for your own application or design system. If you're building a component library for the web from scratch with your own styling, start here.
- React Stately is a library of state management hooks for use in your component library. If you're using React Aria, you'll likely also use React Stately, but it can also be used independently (e.g. on other platforms like React Native).
Read more about our architecture.
Contributing
One of the goals of the React Spectrum project is to make building design systems and component libraries as easy as possible, while maintaining high quality interactions and accessibility support. We aim to raise the bar for web applications. The best way to achieve that goal is together. We would love contributions from the community no matter how big or small. 😍
Read our contributing guide to learn about how to propose bugfixes and improvements, and how the development process works. For detailed information about our architecture, and how all of the pieces fit together, read our architecture docs.
Quick facts
npm install react-ariaCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
How Sourcemap Explorer detects react-aria
We catch react-aria from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/react-aria/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/react-aria/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/react-aria/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/react-aria/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
FAQ
What is react-aria used for?
Spectrum UI components in React
How can I tell if a website is using react-aria?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `react-aria` from two complementary signals: `node_modules/react-aria/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
What is the latest version of react-aria?
3.48.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Where can I read more?
Project homepage: https://github.com/adobe/react-spectrum#readme. Source code: https://github.com/adobe/react-spectrum. Published on npm: https://www.npmjs.com/package/react-aria. Licensed as Apache-2.0.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for react-aria and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.