@headlessui/react
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
About
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
What detecting @headlessui/react tells you about a site
@headlessui/react reveals Tailwind Labs' unstyled, accessible component primitives — the official companion to Tailwind CSS for menus, dialogs, listboxes and transitions. Its presence almost always means a Tailwind-styled app that wanted accessible interactive components without adopting a full design system.
Why the exact @headlessui/react version matters
Headless UI v2 reworked several component APIs and improved the anchor/positioning model; the exact version tells you which component contract the code targets.
@headlessui/react in a real-world stack
When you find @headlessui/react in a bundle, it rarely travels alone. tailwindcss (always, in practice) and @heroicons/react for the icons.
Quick facts
npm install @headlessui/reactCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @headlessui/react pulls in
@headlessui/react declares 5 direct dependencies — each one also rides into any bundle that ships @headlessui/react, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @headlessui/react
@headlessui/react ships as v2.2.10, published 2026-04-07 and carries 5 direct dependencies, 2 peer dependencies (react, react-dom), 819 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @headlessui/react rides inside a deployed bundle — here is how the detection works.
We catch @headlessui/react from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@headlessui/react/ 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 — that map is where the `@headlessui/react` paths live.
- 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/@headlessui/react/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@headlessui/react/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/@headlessui/react/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @headlessui/react
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @headlessui/react version a site actually ships against the ecosystem.
Recent versions
@headlessui/react README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
@headlessui/react
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
Installation
npm install @headlessui/react
Documentation
For full documentation, visit headlessui.dev.
Community
For help, discussion about best practices, or feature ideas:
FAQ
What is @headlessui/react used for?
A set of completely unstyled, fully accessible UI components for React, designed to integrate beautifully with Tailwind CSS.
How can I tell if a website is using @headlessui/react?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@headlessui/react` from two complementary signals: `node_modules/@headlessui/react/` 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.
How do I find out which version of @headlessui/react a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@headlessui/react/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@headlessui/react/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 2.2.10, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @headlessui/react?
2.2.10, 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.
Is @headlessui/react actively maintained?
Actively maintained — the package is shipping new releases at a steady cadence. The last published release was 2026-04-07. Source code: https://github.com/tailwindlabs/headlessui.
Where can I read more?
Project homepage: https://github.com/tailwindlabs/headlessui#readme. Source code: https://github.com/tailwindlabs/headlessui. Published on npm: https://www.npmjs.com/package/@headlessui/react. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @headlessui/react and report the precise version (the registry's latest is v2.2.10, published 2026-04-07; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.