tailwindcss-forms VS felte

The forms plugin is similar to the typography plugin. Because Tailwind CSS’ resets also affect form elements, the job of the forms plugin is to give form elements a set of pretty, default styles. The default styles are minimal so you won't want to use them as is, but they make a convenient base you can override and extend.

Let's copy a form component from HyperUI, and edit it to make it work for us. If you use one of their form components, make sure to install the TailwindCSS forms plugin.

Install tailwind css and tailwindcss/forms.

If you're in a hurry: https://github.com/tailwindlabs/tailwindcss-forms

Finally Tailwind is the last CSS framework it can generate, which also has checkbox labels to the right: https://tailwindcss-forms.vercel.app/

We'll also utilize Tailwind's Forms Plugin to make it easier to style our Auth component, so let's install that as well:

I want to install tailwindcss-forms plugin on Deno but couldn't.

How does it compare to Felte?

Don’t know if it can help, but I discovered this only recently, which was really missing for me with svelte: https://felte.dev/

I’ve been experimenting with web components in order to build a wrapper for Felte that can easily be used with vanilla JS. One of Felte’s features is the ability to use custom field components that are not based on the browser’s native inputs (input, textarea, select). The example I show is a div with an attribute [contenteditable=“true”]. While testing this experiment I found some weird behaviour coming from Firefox: while I could perfectly click each field and type of it, if I tried to use the form only using the keyboard (tabbing to each field) the focus moved but trying to type would always result in the text being added to the first field I focused.

There’s an example on Felte’s repo setting this up!

Ah. Of course 😅. mwc-textfield is not a native input. Felte relies on native inputs. You can use createField (by creating your own "wrapper" Svelte component that will render your ) or... better yet... you can experiment with what I've been working for the past weeks.

For the past few weeks I’ve taken the (arguably pointless) work of migrating Felte from using Jest to uvu. This is a really tedious work by itself, but one of details that would have made this work even more tedious is that Jest prefers assertions to the style of expect(…).toBe* while uvu gives you freedom to choose any assertion library, although there’s an official uvu/assert module that comes with assertions to the style of assert.is(value, expected).

After more than a year of work, I am proud to announce the release of version 1.0.0 of Felte!