@radix-ui/react-dialog

About

@radix-ui/react-dialog is a JavaScript package published to the npm registry. Sourcemap Explorer surfaces it whenever a bundle exposes a matching package.json, node_modules path, or import statement in the original source.

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

@radix-ui/react-dialog reveals an unstyled, accessibility-first primitive — Radix ships the focus-trapping, ARIA-correct behaviour and leaves the styling to you. Finding it (and other @radix-ui/* primitives) is the clearest fingerprint of a shadcn/ui-style design system, where Radix behaviour is paired with Tailwind styling.

Why the exact @radix-ui/react-dialog version matters

Radix primitives are versioned per-package and evolved their controlled/uncontrolled and portal APIs over time; the exact version tells you which behavioural contract the components rely on.

@radix-ui/react-dialog in a real-world stack

When you find @radix-ui/react-dialog in a bundle, it rarely travels alone. Other @radix-ui/react-* primitives, tailwindcss, class-variance-authority and clsx — the canonical shadcn/ui stack.

Quick facts

Common pairings

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

What @radix-ui/react-dialog pulls in

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

How Sourcemap Explorer detects @radix-ui/react-dialog

@radix-ui/react-dialog ships as v1.1.23, published 2026-07-24 and carries 15 direct dependencies, 4 peer dependencies (react, react-dom, @types/react), 405 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @radix-ui/react-dialog rides inside a deployed bundle — here is how the detection works.

We catch @radix-ui/react-dialog from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@radix-ui/react-dialog/ 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 `@radix-ui/react-dialog` 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/@radix-ui/react-dialog/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@radix-ui/react-dialog/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/@radix-ui/react-dialog/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of @radix-ui/react-dialog

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @radix-ui/react-dialog version a site actually ships against the ecosystem.

Recent versions

@radix-ui/react-dialog README

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

npm install -g pnpm

pnpm install

FAQ