Looking for Maintainers

[muhammadsammy]

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!

[AdrienLemaire]

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.
It would be great if @adamwathan and @reinink could consider sponsoring this repo or integrating in to tailwindcss for official typescript support.

[stemount]

@muhammadsammy

@AdrienLemaire I definitely agree with a port of this being committed to tailwindcss upstream should it work nicely with all the known modern frameworks

1. How much work is maintenance of this project per month?
2. I'd volunteer some time here for pull request review.
3. I opened up to the @eddiejaoude community to find maintainers

Awesome work on it gaining traction!

[muhammadsammy]

@stemount

1. How much work is maintenance of this project per month?

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.

2. I'd volunteer some time here for pull request review.

That's awesome. Thank you! I've sent you an invite.

3. I opened up to the @eddiejaoude community to find maintainers

That's very nice! Really appreciate it

[aldebogdanov]

Hello.
I cant help in TypeScript, but I have a question.
Where are you taking full class list? I need it for Elm package. To be honest, for previous version I parsed your index.ts.
But now Tailwind CSS 2.0.1 released and I have new project on it. So, can you share your secret?
Thank you.

[muhammadsammy]

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.
All classes are listed on the documentation site, but I do not know other way to get all classes at once, maybe you can check tailwindcss repo

old reply:

Thanks @laniakea-landscape for your interest!

I get the new changes from their release notes.
Then the list of types in src/index.ts gets generated by the CLI:

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 src/cli/lib/defaultTailwindConfig.ts with the latest tailwind config
The CLI will use this file to generate these classes automatically:

• new pseudoclass variants e.g. hover:flex, focus:flex, md:flex etc.
• new classnames that are based on new values in config. e.g. in tailwind v2 they added font sizing like text-7xl. the new config will have this value and thus will be generated by the CLI.

This generates most of the new classes

---

The above will update existing classes that got new vlaues.
For other new class names:

• classes that their name cannot be customized should be added to src/cli/lib/non-configurable/CORRESPONDING_CATEGORY.ts.
  An example for these would be flex, block (non-configurable/layout) or capitalize (non-configurable/typography).

• classes that their name can be customized (like bg-red-100, sizing classes w-6, etc.) each should be added to corresponding category method in ClassesGenerator class.

---

After doing this for new classes, the CLI would be compatible with new tailwind release.
Now src/index.ts can be updated with the new types by running yarn generate.

[muhammadsammy]

I'm closing this as I'm going to continue maintaining the project.
Just a day ago, my country postponed all exams due to increased covid cases, so I will have some time at least until Feb.

The support for tailwindcss v2 progress will be tracked at #66