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.

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

feat(tailwind): migrate to v4 #7507

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

bjohansebas
Copy link
Member

@bjohansebas bjohansebas commented Feb 23, 2025

Description

Upgrade to tailwind-css major 4. And simplified use of postcss.

Check List

  • [] I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • [] I have run npm run format to ensure the code follows the style guide.
  • [] I have run npm run test to check if all tests are passing.
  • [] I have run npx turbo build to check if the website builds without errors.
  • [] I've covered new added functionality with unit tests if necessary.

Copy link

vercel bot commented Feb 23, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Mar 30, 2025 0:20am

@AugustinMauroy
Copy link
Member

something that may help you:

npx @tailwindcss/upgrade

and for css module: https://tailwindcss.com/docs/compatibility#css-modules

@bjohansebas
Copy link
Member Author

Yep, with that I made the first commit, I thought it was going to do most of the work

Copy link
Contributor

Note

Your Pull Request seems to be updating Translations of the Node.js Website.

Whilst we appreciate your intent; Any Translation update should be done through our Crowdin Project.
We recommend giving a read on our Translation Guidelines.

Thank you!

@ovflowd
Copy link
Member

ovflowd commented Mar 1, 2025

Hey @bjohansebas I assume this is still a WIP?

Copy link
Contributor

github-actions bot commented Mar 1, 2025

Unit Test Coverage Report

Title Lines Statements Branches Functions
@node-core/ui-components Coverage: 95%
95.83% (161/168) 77.86% (102/131) 88.57% (31/35)
@nodejs/website Coverage: 87%
84.61% (495/585) 76.03% (165/217) 86.99% (107/123)
Title Tests Skipped Failures Errors Time
@node-core/ui-components 24 0 💤 0 ❌ 0 🔥 4.436s ⏱️
@nodejs/website 156 0 💤 0 ❌ 0 🔥 6.184s ⏱️

@bjohansebas
Copy link
Member Author

Yep, I'll continue with this later.

@ovflowd
Copy link
Member

ovflowd commented Mar 1, 2025

Yep, I'll continue with this later.

tysm for your contributions <3

@bjohansebas
Copy link
Member Author

I think I'll continue after you all have done the migration to the new version of Next.js.

@AugustinMauroy
Copy link
Member

@bjohansebas bump claudio had merge the pr. You can have fun with git conflict 😁

@AugustinMauroy AugustinMauroy added the github_actions:pull-request Trigger Pull Request Checks label Mar 29, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Mar 29, 2025
@AugustinMauroy AugustinMauroy changed the title [WIP]: tailwind v4 feat(tailwind): migrate to v4 Mar 29, 2025
--shadow-lg:
0px 4px 6px -2px var(--color-shadow, rgba(0, 0, 0 / 3%)),
0px 12px 16px -4px var(--color-shadow, rgba(0, 0, 0 / 8%));
--font-open-sans: var(--font-open-sans);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Is this going to cause a Catch-22? (As in, is --font-open-sans going to depend on itself?)
  2. Can you re-add my TODO comment?

Ditto for IBM Plex Mono

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm sorry Aviv, but I have no idea what you mean.

Copy link
Member

@avivkeller avivkeller Mar 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, let me explain:

  1. Catch-22: We are setting --font-open-sans to --font-open-sans. Is this going to end up having it depend on itself, and do nothing, i.e. if you run var a = a in JS (where a is not defined), or is that not the case in CSS?
  2. I had a TODO comment on the Tailwind config file, can you re-add it to this part of the CSS?

@avivkeller
Copy link
Member

I've denied some changes on Chromatic, if you could take a look:

  1. Pagination has lost it's green color (i.e. https://www.chromatic.com/test?appId=64c7d71358830e9105808652&id=67e874b4b8c794928f6d6905)
  2. Notifications have lost their shadow (i.e. https://www.chromatic.com/test?appId=64c7d71358830e9105808652&id=67e874b4b8c794928f6d6947)
  3. The background for blog-post images has been squished (i.e. https://www.chromatic.com/test?appId=64c7d71358830e9105808652&id=67e874b4b8c794928f6d6955)
  4. The text size got jumbled (https://www.chromatic.com/test?appId=64c7d71358830e9105808652&id=67e874b4b8c794928f6d69d5)

@AugustinMauroy
Copy link
Member

Yes, I had just made the same list by private message Sebastian on slack but I'm waiting for claudio's validation for the changes on the package.json before going further

@ovflowd ovflowd marked this pull request as ready for review March 30, 2025 00:18
@ovflowd ovflowd added the github_actions:pull-request Trigger Pull Request Checks label Mar 30, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Mar 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants