chore: migrate to Tailwind CSS v3 and update config - #1194
chore: migrate to Tailwind CSS v3 and update config#1194lightning-sagar wants to merge 10 commits into
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
|
maintainers, please let me know if you would prefer migrating directly to tailwindcsss v4. since the issue mentions upgrading to v3, I have completed the migration accordingly. but, tailwind v4 has been released, so if the project intends to move to the latest version instead, I can update the migration work to v4 in a follow up pr or adjust this one as needed. |
|
AceTheCreator
left a comment
AceTheCreator
left a comment
There was a problem hiding this comment.
Thanks for picking this up @lightning-sagar, i left you some reviews 👍🏾
|
@AceTheCreator thanks, I understand the task, but I was a confused what's the main reason... so just wanted to double check that I am on the same page.... |
|
@lightning-sagar any update on this? |
|
|
@AceTheCreator please review again.. i have updated all the changes mentioned above. |
|
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
2 participants
Description
Changes proposed in this pull request:
tailwindcss@3.4.17postcss@8autoprefixer@10@tailwindcss/typography@0.5.9purgeoption with the newcontentfield intailwind.config.jsdarkModeconfiguration (darkMode: false)fontSizevalues only those are already provided by tailwind v3borderColorsignature fromtheme => ({})to({ theme }) => ({})borderColortotypographythese changes are done for the Library Dir, and the rest are already using tailwind-v3.
Related issue(s)
Resolves #1150