A Tailwind CSS preset for seamless integration with Mantine UI components.

npm install tailwind-preset-mantine

To use the preset in your Tailwind CSS configuration, add it to the presets array:

// tailwind.config.ts
import tailwindPresetMantine from 'tailwind-preset-mantine';

export default {
	presets: [
		tailwindPresetMantine(),
	],
};

Now you can use tailwind with mantine's style applied:

import { Button } from '@mantine/core';

export default function Page() {
	// `bg-red-500` will be `background-color: var(--mantine-color-red-5)`
	// `text-white` will be `color: var(--mantine-color-white)`
	return <Button className="bg-red-500 text-white">Hello</Button>
}

If you have a custom mantine theme (https://mantine.dev/theming/theme-object/), you should pass it as an option to make custom colors and custom breakpoints available to tailwind.

Let's define your custom mantine colors and breakpoints first:

// src/theme.ts
import {
  type MantineThemeColors,
  type MantineBreakpointsValues,
} from "@mantine/core";

export const colors: MantineThemeColors = {
	// ...your custom colors
}
export const breakpoints: MantineBreakpointsValues = {
	// ...your custom breakpoints
}

Pass your custom colors and breakpoints to MantineProvider:

// src/mantine-provider.tsx
import {
	MantineProvider,
	mergeMantineTheme,
	DEFAULT_THEME,
} from '@mantine/core';
import { colors, breakpoints } from './theme';

const theme = mergeMantineTheme(
  DEFAULT_THEME,
  createTheme({
    breakpoints,
    colors,
  }),
);

export default function MantineProvider({ children }: { children: React.ReactNode }) {
	return <MantineProvider theme={{ colors, breakpoints }}>{children}</MantineProvider>
}

Then pass them to tailwind-preset-mantine:

// tailwind.config.ts
import tailwindPresetMantine from 'tailwind-preset-mantine'
import { colors, breakpoints } from './src/theme';

export default {
	presets: [tailwindPresetMantine({
		mantineColors: colors,
		mantineBreakpoints: breakpoints
	})],
};

Why separate the colors and breakpoints definition in a single file?

Because if passing the whole mantineTheme object, the property mantineTheme.components might include (s)css modules, which could fail to resolve due to the absence of an (s)css loader when loading the Tailwind config file.

If you have a better solution, please let me know in the issue.

You will encounter style conflicts when using mantine and tailwind together. (See this tough discussion.) To prevent this, you can follow the steps below:

Change your global.css to use CSS layers to prevent style conflicts:

@layer tw_base, mantine, tw_components, tw_utilities;

/* import tailwind */
@import "tailwindcss/base" layer(tw_base);
@import "tailwindcss/components" layer(tw_components);
@import "tailwindcss/utilities" layer(tw_utilities);

/* import mantine */
@import "@mantine/core/styles.layer.css";

What's @layer?

Note that here we setup tailwind slightly different from the official docs. We use the CSS @layer directive to control the order of the css. This is because we want to make sure that the mantine styles doesn't get overridden by tailwind reset (tw_base). In this case, the order is tw_base -> mantine -> tw_components -> tw_utilities

To make it work, you also need to change the postcss config like this:

// postcss.config.js
module.exports = {
	plugins: {
		'postcss-import': {},
		'postcss-preset-mantine': {},
		// for tailwind
+		autoprefixer: {},
+		'tailwindcss/nesting': {},
+		tailwindcss: {},
	},
}

Here's a minimal template that you can use to get started:

https://github.com/songkeys/next-app-mantine-tailwind-template

MIT