@mantine/hooks
A collection of 50+ hooks for state and UI management
About
A collection of 50+ hooks for state and UI management
Live mirror of the GitHub README. 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
Quick facts
npm install @mantine/hooksCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
How Sourcemap Explorer detects @mantine/hooks
We catch @mantine/hooks 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/hooks/ 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.
- 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/hooks/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@mantine/hooks/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/hooks/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
FAQ
What is @mantine/hooks used for?
A collection of 50+ hooks for state and UI management
How can I tell if a website is using @mantine/hooks?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@mantine/hooks` from two complementary signals: `node_modules/@mantine/hooks/` 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.
What is the latest version of @mantine/hooks?
9.2.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.
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/hooks. Licensed as MIT.
Keep reading on Sourcemap Explorer
Practical guides
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @mantine/hooks and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.