Use local build / tailwind and postcss config file instead of CDN

After I run serve from within the output directory, everything magically works!

As a suggestion, I don’t see a tailwind config file anywhere…and it definitely seems like that is the recommended option: https://tailwindui.com/documentation#add-the-tailwindcss-ui-plugin https://tailwindui.com/documentation#update-your-purgecss-configuration

Would it be possible to get this working with a local tailwind config file and PurgeCSS configuration, so we eliminate the CDN? https://cdn.jsdelivr.net/npm/@tailwindcss/ui@latest/dist/tailwind-ui.min.css

Once again, many thanks for the repo!

[connecteev]

Agreed. Look forward to the push for local builds / configs with tailwindcss and postcss/purgecss (and tailwind prefix support!)

Btw even if the private git repo becomes available, I think the work you’ve done here is of a lot of value to track changes to the tailwindui components and save time getting the components locally.

[kiliman]

Yes, the index page was kind of a last minute addition based on a comment in the discord chat. I simply wanted to be able to view the components locally, especially as a quick way to verify that the crawler and transformer worked properly.

The local config will need to be supported in order to fully support tailwind prefixes #15 anyway.

Now that most of the transformers have been built, I can start cleaning up some of the code and make it even more flexible.

I think Adam is going to open up a private repo now that GitHub is free for teams. So the download part won’t be necessary but the transformers will definitely help.