The color-adjust shorthand is currently deprecated
See original GitHub issueWhat version of Tailwind CSS are you using?
v3.0.24
What build tool (or framework if it abstracts the build tool) are you using?
Nuxt3 with Vite
What version of Node.js are you using?
18.0.0
What browser are you using?
Chrome
What operating system are you using?
Linux
Reproduction URL
It is not a problem with TailwindCSS but with a property that is deprecated.
Describe your issue
WARN [vite:css] Replace color-adjust to print-color-adjust. The color-adjust shorthand is currently deprecated.
1 | @tailwind base;
| ^
2 | @tailwind components;
3 | @tailwind utilities;
Issue Analytics
- State:
- Created a year ago
- Reactions:12
- Comments:5
Top Results From Across the Web
autoprefixer: Replace color-adjust to print ... - Stack Overflow
autoprefixer: Replace color-adjust to print-color-adjust. The color-adjust shorthand is currently deprecated. webpack compiled with 1 warning.
Read more >autoprefixer: Replace color-adjust to print-color-adjust. #36259
Replace color-adjust to print-color-adjust. The color-adjust shorthand is currently deprecated. Below solution didnt't work add in package.json
Read more >Fixing the color-adjust shorthand is currently deprecated ...
The issue itself is rather trivial. It's a deprecated CSS shorthand property being used. I didn't want to downgrade Autoprefixer. In my ...
Read more >Solved — autoprefixer: Replace color-adjust to print-color ...
The color -adjust shorthand is currently deprecated. npm install autoprefixer@10.4.5 — save-exact — fails.
Read more >autoprefixer: replace color-adjust to print-color ... - You.com
The color -adjust shorthand is currently deprecated and needs to be replaced with the print-color-adjust shorthand [1][2]. This will ensure that your code...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This seems to have been caused by this change in autoprefixer 10.4.6.
I started getting the same warning as of this morning after I upgraded to 10.4.6