[Bug Report][4.1.12] Utility classes are broken with @use 'vuetify/settings' with ( $grid-breakpoints: variables.$grid-breakpoints )
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 41k
- Forks
- 7.1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 11
Description
Environment
Vuetify Version: 4.1.12
Vue Version: 3.5.41
OS: Windows
Steps to reproduce
You can look at the screenshots or clone the repo and play with vuetifyTheme.scss and adding / removing the $grid-breakpoints.
Alternatively you could just try and set the $grid-breakpoints property using a custom vuetify/settings style
Expected Behavior
I want to have a single source of truth for my breakpoints defined in my design system that is properly propagated to Vuetify side.
For now I'm fine with hardcoding the values and using 2 separate sources of truth(Vuetify + my own custom design system) but it's weird that I can't align Vuetify with my variables.
I'm not sure if this is the proper way of doing it and I would appreciate the help - LLM seems to be confused by this behavior as well.
Actual Behavior
When I try to set the $grid-breakpoints it breaks at the very least the utility classes and maybe more
Images
I've specifically reduced the breakpoints and painted the container red. The only change that leads to that drastic effect is setting up the $grid-breakpoints which appears to completely break everything.

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Clone the linked reproduction and start with vuetifyTheme.scss, comparing the build with and without the custom $grid-breakpoints passed through vuetify/settings. Trace how the customized breakpoints reach the utility classes, then verify that the intended breakpoint values are propagated without breaking those classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scss
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100