@mantine/core
React components library focused on usability, accessibility and developer experience
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
npm install @mantine/coreThis 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.7.1, published 2026-10-06 and carries 5 direct dependencies, 3 peer dependencies (react, react-dom, @mantine/hooks), 481 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
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
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
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.
Mantine
Links
Packages
@mantine/hooks– collection of 80+ hooks for state and UI management@mantine/core– core components library – 100+ components@mantine/form– forms management library@mantine/charts– recharts based charts library@mantine/notifications– a fully featured notifications system@mantine/spotlight–Ctrl + Kcommand center for your application@mantine/code-highlight– code highlight built with highlight.js@mantine/tiptap– a Tiptap based rich text editor@mantine/dropzone– manages files drag 'n' drop to an area or entire screen@mantine/carousel– Carousel component@mantine/nprogress– navigation progress@mantine/modals– centralized modals manager@mantine/schedule– Schedule component for displaying events
Getting help
Mantine has a very friendly community, we are always happy to help you get started:
- Join Discord community – it is the easiest way to get help, all questions are usually answered in about 30 minutes
- GitHub Discussions – ask anything about the project or give feedback
Contributors
Support development
Mantine is a MIT-licensed open source project with its ongoing development made possible entirely by the support of these awesome backers. If you'd like to join them, please consider contributing financially on OpenCollective.
License
MIT
FAQ
What is @mantine/core used for?
React components library focused on usability, accessibility and developer experience
How can I tell if a website is using @mantine/core?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@mantine/core` from two complementary signals: `node_modules/@mantine/core/` 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 @mantine/core a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@mantine/core/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/@mantine/core/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 9.7.1, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @mantine/core?
9.7.1, 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 @mantine/core actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-10-06. Source code: https://github.com/mantinedev/mantine.
What is the relationship between @mantine/core and Mantine?
@mantine/core is the canonical npm package for Mantine. Sourcemap Explorer treats finding `@mantine/core` in a bundle as the framework-level signal that Mantine is on the page, and the page you're reading is the canonical Sourcemap Explorer entry for the package itself.
Where can I read more?
Project homepage: https://mantine.dev/. Source code: https://github.com/mantinedev/mantine. Published on npm: https://www.npmjs.com/package/@mantine/core. Licensed as MIT.
Keep reading on Sourcemap Explorer
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @mantine/core and report the precise version (the registry's latest is v9.7.1, published 2026-10-06; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.