Mostly fix TailwindCSS v4 Build issues #1990
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey Nuno - I've been having a hack at this, however there are 2 problems I don't seem to be able to resolve myself. Hope this PR might help you complete the v4 migration.
Seems the old CLi is entirely incompatible with v4, now being a separate package and all. After resolving the CLi package problem, several issues sprung up (in order, as previous is resolved):
Error: Can't resolve 'components/zen-mode.css' in 'H:\Git\blowfish\assets\css'
@import 'components/zen-mode.css';
to@import './components/zen-mode.css';
Error: Cannot apply unknown utility class: rtl:pr-4
+ Various othersmain.css
to only@import "tailwindcss";
Error: Cannot apply unknown utility class: bg-primary-100
+ all other overridestailwind.config.js
is no longer used.@config "../../tailwind.config.js";
Now this seems to actually work for the most part, only 2 issues I've been able to spot on the example site is 1. the homepage
background
layout:And 2. breadcrumbs:
I couldn't really progress much from here, so I tried the
@tailwindcss/upgrade
tool. It does make ALOT more changes for a "full" migration, but produces the EXACT SAME result as the above.This does raise a new concern when/if deprecated classes are removed, but one thing at a time, right?
edit - fix grammar