@mantine/core

About

React components library focused on usability, accessibility and developer experience

What detecting @mantine/core tells you about a site

@mantine/core reveals a comprehensive, modern React component and hooks library — a fast-growing alternative to MUI and Chakra with a large built-in component set and strong TypeScript support. Its presence signals a team that wanted a complete, well-documented UI kit with native dark-mode and form handling out of the box.

Why the exact @mantine/core version matters

Mantine v7 moved from Emotion to native CSS modules with CSS variables, a major architectural change; the exact version tells you which styling approach and theme API the app uses.

@mantine/core in a real-world stack

When you find @mantine/core in a bundle, it rarely travels alone. Other @mantine/* packages (hooks, form, dates, notifications) and a build that handles its CSS layer.

Quick facts

This package powers Mantine

The @mantine/core package is the canonical implementation of Mantine. Sourcemap Explorer uses this exact npm package as the framework-level fingerprint when it flags Mantine on a page — both via the bundled node_modules/@mantine/core/ source paths and via the embedded package.json inside the JavaScript sourcemap.

Common pairings

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

What @mantine/core pulls in

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

How Sourcemap Explorer detects @mantine/core

@mantine/core ships as v9.5.1, published 2026-08-02 and carries 5 direct dependencies, 3 peer dependencies (react, react-dom, @mantine/hooks), 474 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @mantine/core rides inside a deployed bundle — here is how the detection works.

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

Major releases of @mantine/core

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

Recent versions

@mantine/core README

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

# With yarn
yarn add @mantine/core @mantine/hooks

# With npm
npm install @mantine/core @mantine/hooks

FAQ

Keep reading on Sourcemap Explorer