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 🙏

© 2025 – Pkg Stats / Ryan Hefner

unplugin-mantine-autoload-css

v0.2.0

Published

Unplugin for Mantine to autoload CSS for used components

Downloads

258

Readme

Unplugin Mantine Autoload CSS

NPM Version

Mantine Unplugin to autoload CSS for used components

Usage

vite.config.ts

import { defineConfig } from 'vite'
import { mantineAutoloadCSS } from 'unplugin-mantine-autoload-css'
export default defineConfig({
	plugins: [
		mantineAutoloadCSS(),
	]
})

Behavior options:

all: Boolean / Default: false

Instead of component detecting, load @mantine/core/styles.css for each file with import from @mantine/core

Hint: If you want to use this plugin only for build optimization, you can use it conditionally:

export default defineConfig(({ mode }) => ({
	plugins: [
		mantineAutoloadCSS({
			all: mode === 'development',
		}),
	],
}))

layer: Boolean / Default: true

Switch between .css and .layer.css files

Mantine: CSS Layers

forced: ComponentStylesheetName[] / Default: []

Add some components' CSS for each file with import from @mantine/core

Global styles toggles:

baseline: Boolean / Default: true

Load baseline.css / baseline.layer.css — a minimal CSS reset, sets box-sizing: border-box and changes font properties

defaultCSSVariables: Boolean / Default: true

Load default-css-variables.css / default-css-variables.layer.css — contains all CSS variables generated from the default theme

global: Boolean / Default: true

Load global.css / global.layer.css — global classes used in Mantine components

allDependencies: Boolean / Default: true

Some components like Select do not have any styles on their own – they are built on top of other components. So we cannot automate that without lurking Mantine sources. If you are not sure which components are used in a particular component, you can import all styles for components that are reused in other components. https://mantine.dev/styles/css-files-list/#components-dependencies

Problem

In Mantine, you have to manually import CSS for components you use.

Reason: there is two versions of CSS for each component: .css and .layer.css, so you have to decide what to use. Official answer is “Mantine is not a building tool”, so I decided to fill this gap.

You can just import all Mantine CSS containing every CSS for every Mantine component:

import '@mantine/core/styles.css'

but you will import CSS for components you don't use in your project.

styles.css is 226KB

Solution

Vite plugin looking for imports from @mantine/core for each your source .ts or .tsx file, adding CSS imports based on hypothesis that every component has CSS named after it.

Example: if you add this to MyComponent.tsx:

import { Accordion } from '@mantine/core'

So we want to add this to MyComponent.tsx:

import '@mantine/core/styles/Accordion.css'

In @mantine/core/styles directory, we have all CSS files we want:

Accordion.css
Accordion.layer.css
ActionIcon.css
ActionIcon.layer.css
… and so on

So I automated this.

(Don't worry about import duplication: any bundler will deduplicate them across bundle)