Sourcemap Explorer
Stack · npm package

@radix-ui/react-dialog

latest 1.2.0· MIT· 408 versions publishedView on npm

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

Latest version1.2.0
LicenseMIT
Installnpm install @radix-ui/react-dialog
Direct dependencies15
Peer dependenciesreact, react-dom, @types/react, @types/react-dom

Common pairings

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

reactreact-dom@types/react@types/react-dom

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 .

aria-hidden@radix-ui/react-id@radix-ui/primitivereact-remove-scroll@radix-ui/react-slot@radix-ui/react-portal@radix-ui/react-context@radix-ui/react-presence@radix-ui/react-primitive@radix-ui/react-focus-scope@radix-ui/react-compose-refs@radix-ui/react-focus-guards@radix-ui/react-dismissable-layer@radix-ui/react-use-layout-effect@radix-ui/react-use-controllable-state

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

@radix-ui/react-dialog ships as v1.2.0, published 2026-10-05 and carries 15 direct dependencies, 4 peer dependencies (react, react-dom, @types/react), 408 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.

Major
First release
Date
v1
1.0.0
2022-07-20
v0
0.0.1
2020-12-15

Recent versions

Version
Released
1.2.0
2026-10-05
1.1.23
2026-07-24
1.1.22
2026-07-24
1.1.21
2026-07-22
1.1.20
2026-07-20
1.1.19
2026-07-06
1.1.18
2026-06-30
1.1.17
2026-06-15

@radix-ui/react-dialog README

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

react-dialog

View docs here.

FAQ

What is @radix-ui/react-dialog used for?

@radix-ui/react-dialog is a JavaScript package published to the npm registry. The README and import patterns inside published bundles reveal the intended use case; on Sourcemap Explorer it shows up whenever a site bundles `import` from `@radix-ui/react-dialog` or includes `node_modules/@radix-ui/react-dialog/` in a sourcemap.

How can I tell if a website is using @radix-ui/react-dialog?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@radix-ui/react-dialog` from two complementary signals: `node_modules/@radix-ui/react-dialog/` 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 @radix-ui/react-dialog a website is running?

Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@radix-ui/react-dialog/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/@radix-ui/react-dialog/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 1.2.0, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.

What is the latest version of @radix-ui/react-dialog?

1.2.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.

Is @radix-ui/react-dialog actively maintained?

Very actively maintained — the last release shipped within the past three months. The last published release was 2026-10-05. Source code: https://github.com/radix-ui/primitives.

Where can I read more?

Project homepage: https://radix-ui.com/primitives. Source code: https://github.com/radix-ui/primitives. Published on npm: https://www.npmjs.com/package/@radix-ui/react-dialog. Licensed as MIT.

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for @radix-ui/react-dialog and report the precise version (the registry's latest is v1.2.0, published 2026-10-05; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome