-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Looking for Maintainers #62
Comments
I won't be able to maintain the repo, but I really hope that someone else can take this over. Otherwise, I look forward to you coming back in 3 months. |
@AdrienLemaire I definitely agree with a port of this being committed to tailwindcss upstream should it work nicely with all the known modern frameworks
Awesome work on it gaining traction! |
It depends on how many features in a tailwindcss release and how frequent they release a new version. However, it's not really a lot of time, but I'm very busy taking MBBS exams for the next 3 months.
That's awesome. Thank you! I've sent you an invite.
That's very nice! Really appreciate it |
Hello. |
Edit:Sorry @laniakea-landscape, I misunderstood your comment and went into too much details The list of classes for every release should be listed in the release notes. old reply:Thanks @laniakea-landscape for your interest! I get the new changes from their release notes. First thing is to update tailwindcss and the default config file by running: yarn add -D tailwindcss@^2.0.1 autoprefixer
yarn run updateConfig This will update
This generates most of the new classes The above will update existing classes that got new vlaues.
After doing this for new classes, the CLI would be compatible with new tailwind release. |
I'm closing this as I'm going to continue maintaining the project. The support for tailwindcss v2 progress will be tracked at #66 |
Hello and thanks to all contributors and users of this project!
Unfortunately, I will not be able to maintain this project well for the next three months.
If anyone is interrested in becoming a maintainer, please contact me!
The text was updated successfully, but these errors were encountered: