@floating-ui/react

About

Floating UI for React

What detecting @floating-ui/react tells you about a site

@floating-ui/react is the React binding for Floating UI, the positioning engine that powers tooltips, popovers, dropdowns and menus, so its appearance means the app does serious anchored-overlay work and cares about getting placement, flipping and collision handling right. Because it is a low-level primitive rather than a finished component, finding it signals an engineering team building their own design system or a component library's internals, not someone wiring up off-the-shelf widgets. It is the kind of dependency that quietly underpins many other libraries.

Why the exact @floating-ui/react version matters

Floating UI is the successor to Popper.js and went through a significant rename and API overhaul on the way to its 1.0 line, and the React adapter itself reorganised hooks and interaction APIs across versions. The exact version therefore tells you which generation of the middleware-and-hooks model the code targets and whether it predates or follows the stable React-binding shape.

@floating-ui/react in a real-world stack

When you find @floating-ui/react in a bundle, it rarely travels alone. Often vendored inside Radix UI, Headless UI or a bespoke component library rather than imported directly.

Quick facts

Common pairings

Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.

What @floating-ui/react pulls in

@floating-ui/react declares 3 direct dependencies — each one also rides into any bundle that ships @floating-ui/react, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

How Sourcemap Explorer detects @floating-ui/react

@floating-ui/react ships as v0.27.20, published 2026-07-11 and carries 3 direct dependencies, 2 peer dependencies (react, react-dom), 84 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @floating-ui/react rides inside a deployed bundle — here is how the detection works.

We catch @floating-ui/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/@floating-ui/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. 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 `@floating-ui/react` paths live.

2. 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/@floating-ui/react/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@floating-ui/react/package.json` gives you the exact installed version.

3. 3

   Read the version directly from package.json

   Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@floating-ui/react/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Recent versions

@floating-ui/react README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

FAQ

Keep reading on Sourcemap Explorer