-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict in class order between eslint
and prettier
#278
Comments
Hey! It seems like our Prettier plugin isn't noticing your config file, is it in a non-standard location? You might need to configure your config path with this option: |
Hey, For the background, the require("tailwindcss-fluid-type")({
settings: {
fontSizeMin: 1, // 1.125rem === 18px
fontSizeMax: 1.25, // 1.25rem === 20px
ratioMin: 1.125, // Multiplicator Min
ratioMax: 1.2, // Multiplicator Max
screenMin: 20, // 20rem === 320px
screenMax: 96, // 96rem === 1536px
unit: "rem", // default is rem but it's also possible to use 'px'
prefix: "", // set a prefix to use it alongside the default font sizes
extendValues: true, // When you set extendValues to true it will extend the default values. Set it to false to overwrite the values.
},
values: {
"3xs": [-4, 1.6],
"2xs": [-3, 1.6],
xs: [-2, 1.6],
sm: [-1, 1.6],
base: [0, 1.6],
lg: [1, 1.6],
xl: [2, 1.2],
"2xl": [3, 1.2],
"3xl": [4, 1.2],
"4xl": [5, 1.1],
"5xl": [6, 1.1],
"6xl": [7, 1.1],
"7xl": [8, 1],
"8xl": [9, 1],
"9xl": [10, 1],
},
}), I tried to reproduce but impossible. Closing for now then. Thanks ! |
What version of
prettier-plugin-tailwindcss
are you using?0.6.1
What version of Tailwind CSS are you using?
3.4.3
What version of Node.js are you using?
21.7.1
What package manager are you using?
npm
What operating system are you using?
macOS
Describe your issue
In a
.tsx
file, prettier is ordering in this order :text-2xs mx-1.5 mb-0.5 py-1
.But eslint is complaining :
text-2xs
is an extend of Tailwind theme insidetailwind.config.js
.prettierrc
.eslintrc
It's maybe linked to #270 ?
Thanks !
The text was updated successfully, but these errors were encountered: