Skip to content
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.

Sign up for GitHub

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

Jump to bottom

TailwindCSS v4 migration #3631

Open
2 tasks done
adrianthedev opened this issue Jan 31, 2025 · 0 comments · May be fixed by #3632
Open
2 tasks done

TailwindCSS v4 migration #3631

adrianthedev opened this issue Jan 31, 2025 · 0 comments · May be fixed by #3632

Comments

@adrianthedev
Copy link
Collaborator

adrianthedev commented Jan 31, 2025 •
edited
Loading

Context

Let's prepare for the TW v4 migration.

Help us test it 🙌

Please use the tw4 version and check for any inconsistencies. Ideally, you'll not see any differences from the past versions. This is intended. Basically we want to make sure the transition from TW 3 to 4 is seamless without any changes. Then we'll be able to improve it iteratively.
Thank you for your help!

Ejected Tailwind strategy

TBD

Blockers

  • Confirmation dialog not centered issue
  • sidebar buttons doubled (hidden/flex issue)

Avo gems who are using TailwindCSS

  • pro (light)
  • advanced (medium)
  • dyanmic filters (medium)
  • kanban (heavy)
  • collaborate (will have light)

I think it's best that each gem to switch to their own TW pipeline with prefixed classes.
@adrianthedev adrianthedev linked a pull request Feb 3, 2025 that will close this issue
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Issues
Status: No status
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

refactor: upgrade to TailwindCSS v4 avo-hq/avo
1 participant
@adrianthedev