Mantine no longer depends on Emotion for styles generation. All @mantine/* packages are now shipped with native CSS files which can be imported from @mantine/{package}/styles.css , for example:
This change improves performance, reduces bundle size of the library and allows using Mantine in environments where CSS-in-JS is not supported (or supported with limitations), for example, Next.js app directory.
Important breaking changes:
It is now recommended to use CSS modules to style Mantine components. To update your project to CSS modules , follow the 6.x → 7.x migration guide .
If you prefer CSS-in-JS syntax for styling, you can use Vanilla extract as a TypeScript CSS preprocessor. You will be able to use most of Mantine styling features with Vanilla extract .
All components now support system color scheme – when colorScheme value is auto , components will use prefers-color-scheme media query to determine if the user prefers light or dark color scheme.
Note that auto is not the default value. You need to set it manually to enable system color scheme support both on MantineProvider and in ColorSchemeScript :
MantineProvider now comes with a built-in color scheme manager. It is no longer required to use any other components to set up color scheme logic. Color scheme can be changed with useMantineColorScheme hook :
CSS modules is now the recommended way to style Mantine components, although it is not required – you can choose any other styling solution of your choice.
It is also recommended to use postcss-preset-mantine . It includes mixins and functions to simplify styling of Mantine components. postcss-preset-mantine is included in all templates.
Mantine no longer includes normalize.css. Instead, it uses a bare minimum set of global styles . These styles are part of the @mantine/core package and are applied automatically when you import @mantine/core/styles.css in your application. Note that these styles cannot be decoupled from the rest of the library.
You can now use Mantine as a headless library. To achieve that, just do not import @mantine/*/styles.css in your application. Then you will be able to apply styles with Styles API .
createTheme function is a replacement for MantineThemeOverride type. Use it to create a theme override, it will give you autocomplete for all theme properties:
All components that support default props or Styles API now have a static extend function which allows getting autocomplete when customizing defaultProps , classNames and styles of the component on theme :
You can now get component props in classNames and styles to conditionally apply styles. This feature is a more powerful replacement for styles params.
You can now customize components CSS variables to change component styles based on its props. For example, it can be used to add new sizes :
All components now have data-variant attribute on the root element, even if the component does not have any predefined variants. You can use it to apply styles to all components of the same type on theme :
There are multiple ways to customize component sizes:
Example of customizing Button size with data-size attribute:
Button , Badge , ActionIcon , ThemeIcon and other components now support custom variants with variantColorResolver – it supports both changing colors of existing variants and adding new variants.
It is now possible to scale rem units. It is useful when you want to change font-size of html / :root element and preserve Mantine components sizes. For example, if you would like to set html font-size to 10px and scale Mantine components accordingly, you need to set scale to 1 / (10 / 16) (16 – default font-size) = 1 / 0.625 = 1.6 :
All components that support color prop now support the following color values:
Classes of each component are now available in Component.classes object. For example, you can find Button classes in Button.classes :
You can use these classes to create components with the same styles as Mantine components:
New @mantine/colors-generator package is now available to generate color palettes based on single color value. It is also available as online tool . Note that it is usually better to generate colors in advance to avoid contrast issues.
@mantine/core package now exports DirectionProvider component, which should be used to configure the direction of the application. useDirection hook can be used to toggle direction. All components now include RTL styles by default, it is no longer required to set up additional plugins. See RTL documentation to learn more.
Starting from version 7.0 Mantine no longer supports older React versions. The minimum supported version is now React 18. It is required because Mantine components now use useId and useSyncExternalStore hooks, which are available only in React 18.
Components that previously had rightSection and icon props, now use leftSection instead of icon . Example of Button sections:
NumberInput was migrated to react-number-format . It now supports more features and has improvements in cursor position management. Due to migration, some of the props were renamed – follow the documentation to learn about the changes.
Loader component is now built with CSS only. This change improves performance and reduces HTML output of the component.
Theme object no longer supports theme.loader property – it is also now possible to add custom loaders on theme with default props . Specified Loader will be used in all components that use it under the hood ( LoadingOverlay , Button , ActionIcon , Stepper , etc.).
Progress component now supports compound components pattern. Advanced features that were previously implemented in Progress are now supposed to be implemented with compound components instead.
Table component changes:
Group component changes:
AppShell component was completely rewritten, it now supports more features:
SimpleGrid now uses object format to define grid breakpoints and spacing, it works the same way as style props .
Grid now uses object format in gutter , offset , span and order props, all props now work the same way as style props .
Image component changes:
Carousel now uses object format for responsive values in slideSize and slideGap props instead of breakpoints prop:
@mantine/prism package was deprecated in favor of @mantine/code-highlight package. The new package uses highlight.js instead of Prism .
New Fieldset component:
The new Combobox component allows building custom select, autocomplete, tags input, multiselect and other similar components. It is used as a base for updated Autocomplete , Select , TagsInput and MultiSelect components.
Combobox is very flexible and allows you to have full control over the component rendering and logic. Advanced features that were previously implemented in Autocomplete , Select and MultiSelect are now supposed to be implemented with Combobox instead.
You can find 50+ Combobox examples on this page .
New TagsInput component based on Combobox component. The component is similar to MultiSelect but allows entering custom values.
All inputs now support withErrorStyles prop, which allows removing error styles from the input. It can be used to apply custom error styles without override, or use other techniques to indicate error state. For example, it can be used to render an icon in the right section:
Something went wrong
All Mantine components now support hiddenFrom and visibleFrom props. These props accept breakpoint ( xs , sm , md , lg , xl ) and hide the component when viewport width is less than or greater than the specified breakpoint: