npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@pikku/mantine

v0.12.16

Published

Mantine components with i18n-tightened types for Pikku

Readme

@pikku/mantine

A drop-in for @mantine/core with i18n-tightened types — zero runtime added. Every string-bearing prop (children, label, placeholder, title, aria-label, …) is narrowed from string to the branded I18nString / I18nNode from @pikku/react, so untranslated literals fail to compile.

// before — plain Mantine compiles this
import { Button } from '@mantine/core'
;<Button>Save</Button>

// after — @pikku/mantine rejects the raw string
import { Button } from '@pikku/mantine/core'
import { m } from '@/i18n'
;<Button>{m.actions_save()}</Button> // ✅ branded
;<Button>Save</Button> // ❌ type error

I18nString is structurally Paraglide JS's LocalizedString, so a Paraglide m() message satisfies the gate natively — your app owns the locale store and @pikku/react only owns the brand.

Aliasing @mantine/core → @pikku/mantine/core (e.g. via build-time resolution) therefore turns the whole app into a strict translation gate. Use asI18n() from @pikku/react as a deliberate escape hatch for dynamic, non-i18n strings (server errors, user content).

Install

yarn add @pikku/mantine @pikku/react
# peers: @mantine/core@^8 || ^9, react

@pikku/mantine/dev

A second entry point for development-only controls. It is deliberately separate from /core: that one's contract is "drop-in alias for @mantine/core", so it must not export components Mantine has no counterpart for.

<DevActorSwitcher /> is the one-click "Sign in as …" control — it signs in as any declared scenario persona with no password, so an app can be reviewed as each kind of user. pikku fabric validate requires any frontend with a login screen to ship one, since without it a reviewer is locked out of their own sandbox.

import { DevActorSwitcher } from '@pikku/mantine/dev'
;<DevActorSwitcher
  apiUrl={apiUrl()}
  app={appSlug}
  onSignedIn={() => navigate({ to: '/' })}
/>

No credential reaches the bundle: it lists personas from /auth/sign-in/personas and signs in by persona id through /auth/sign-in/persona. Both are served by pikkuActor({ personaSignIn }) from @pikku/better-auth. Outside pikku dev the server offers nobody unless the stage opts into actor sign-in and turns its devSwitcher flag on, so the control renders null in production.

It takes onSignedIn rather than depending on a router — every app lands somewhere different. For custom UI, build on useDevActors() from @pikku/react instead; this component is only its default rendering.

How it works

The package re-exports the real Mantine component values and only re-casts their types. Polymorphism (component="a"), compound statics (Menu.Item, Tabs.List, Menu.Divider, …) and every other Mantine feature are preserved — see src/core/helpers.ts for the type machinery and src/core/i18n.test-d.tsx for the enforced positive/negative contract (yarn test).