Using Formkit instead

[laportem]

Awesome starter. Ever thought of using @formkit/nuxt instead of the default @tailwindcss/forms
Formkit is much more complete.

[bryantgillespie]

Looks like a neat library. I like that validation is built in.

Do you have much experience with it @laportem?

Curious to know how easy it is to add custom inputs or style with Tailwind.

[laportem]

I'm new to this version although I use the old nuxt2 version extensively. Nuxt2 uses https://vueformulate.com/

The custom input looks ok
https://formkit.com/guides/create-a-custom-input

[andrew-boyd]

Hello there! I'm here because my FormKit senses were tingling 😉. Happy to help answer anything I can.

Re: Tailwind styling — we've worked hard to make it as easy as possible to apply utility classes at every level of the DOM hierarchy that a FormKit component outputs and have written a guide specifically about Tailwind. The core concept here will remain the same but we are about to move generateClasses to @formkit/core in the next release because it's not Tailwind specific. The @formkit/tailwindcss package will also be deprecated in the next release and you'll instead import the plugin for Tailwind from @formkit/themes along with support for other Utility Class Systems such as Windi and Uno.

https://formkit.com/guides/create-a-tailwind-theme

Happy to chat in the Discord as well, we're very active there and would be able to chat in real-time if you've got any implementation questions: https://discord.gg/2q3UZkUQbR

[bryantgillespie]

Maybe we can add a different branch that supports FormKit to give someone the option.