-
Notifications
You must be signed in to change notification settings - Fork 149
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
Problem with tailwindcss-custom-forms #22
Comments
Moving issue to windmill-react-ui. I'm already working on the update to v2, and this will be addressed too. |
first things first - congrats for your awesome work! do you have already any eta about when you may have a fix or workaround for this? or still looking at it ? all the best |
@AntonioMeireles thank you! I'm currently moving to another country, so time is short, but I would like to have this done by January 1st. |
many thanks for your prompt reply! Meanwhile, Good luck with your move/new endeavour && a Merry Christmas / Happy 2021! |
I'm also getting this error when trying to get it set up with latest [email protected].
@estevanmaito any suggestions on how to do a quick fix to get this up and running? Happy to help with a PR to get this going for 2.0, as I'd love to leverage this library as the base for our design system. Just integrated tailwind and really loving it so far. Thanks for the awesome library! I also learned a lot looking through your Tailwind UI dashboard code. Great work! |
It would be really great to get Tailwind v2 support, there were quite a lot of improvements in the new version. |
@estevanmaito are you needing any help with the transfer to tailwind css v2? Have started using WIndmill React Dashboard as a baseline for my project so far so can help with the semantics. If there are any parts of code that can be forked and won't cause conflict, I would be happy to help |
Tailwind-custom-froms breaks on TailwindCSS v2 and people are switching to official forms plugin. If anyone seeing "value.charCodeAt" error, this might be the reason.
The text was updated successfully, but these errors were encountered: