chore: update tailwind and related dependencies to latest versions#7984
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| new CssMinimizerPlugin({ | ||
| minify: CssMinimizerPlugin.lightningCssMinify, | ||
| }), | ||
| ], |
There was a problem hiding this comment.
Why CssMinimizerPlugin.lightningCssMinify was removed?
There was a problem hiding this comment.
it doesn't support the new media query syntax in v4 @media (width >= 768px)
compared to earlier one - @media (min-width: 768px)
Build was failing because of this
There was a problem hiding this comment.
I think we need to update it or look at options, maybe we need to enable something here
| render() { | ||
| return ( | ||
| <section className="splash-viz dark:bg-gray-900"> | ||
| <section className="splash-viz dark:bg-gray-900!"> |
There was a problem hiding this comment.
Please describe all CSS changes to understand why it was changed, thanks
| {link.children.map((child) => { | ||
| const classNames = | ||
| "text-blue-400 py-5 text-sm capitalize hover:text-black dark:hover:text-white"; | ||
| "text-blue-400 dark:text-[#69a8ee] py-5 text-sm capitalize hover:text-black dark:hover:text-white"; |
| ul, | ||
| ol { | ||
| padding-left: 30px; | ||
| list-style: revert; |
There was a problem hiding this comment.
it wasn't showing the markers
production:
|
|
||
| img { | ||
| width: auto; | ||
| display: inline-block; |
| padding: 0; | ||
| font-size: inherit; | ||
| display: flex; | ||
| align-items: center; |
| } | ||
|
|
||
| .dropdown__arrow { | ||
| line-height: 1; |
|
Please remove - https://github.com/webpack/webpack.js.org/blob/main/.github/dependabot.yml#L12 and we can merge |
|
removed tailwind css and also fixed the link color 
prod: |
| - dependencies | ||
| versioning-strategy: widen | ||
| ignore: | ||
| - dependency-name: "tailwindcss" |
There was a problem hiding this comment.
Remove ignore too, we don't have modules to ignore anymore
2 participants
Closes: #7974
Summary
This PR
What kind of change does this PR introduce?
chore
Did you add tests for your changes?
no
Does this PR introduce a breaking change?
yes
In
Tailwind v3, utilities were NOT wrapped in@layerbut inTailwind v4, all utilities are wrapped in@layer utilities, so after upgrade unlayered styles (Scss) held higher specificity than Tailwind utilities, which were fixed on th PRIf relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI
i have used sonet 4.6 for debugging.