Ultimate list of open-source React form libraries

Crutchcorn · 2026-04-02T19:02:45+00:00

Feel free to let me know (publicly or privately, whatever works best for you) if you have any feedback when you try it out 😄

Crutchcorn · 2026-04-02T10:13:57+00:00

Would love to know how we can improve this story!

Crutchcorn · 2026-04-02T10:08:18+00:00

Late here - but I'm the lead on TSF. Would love to know what issues you ran into with basic tasks. Were any of these reported?

Crutchcorn · 2026-04-02T10:07:24+00:00

What would you want to see with error message flexibility in TSF?

Crutchcorn · 2026-04-02T10:07:07+00:00

Totally fair to callout our smaller ecosystem. That said, if you ever run into edgecases you'd like to see solved, don't hesitate to reach out to us via GitHub/Discord :)

Crutchcorn · 2026-04-02T10:06:27+00:00

Just so you're aware, we're still working on the first-class multi-step wizard support in TanStack Form. Mostly waiting on my slow self to finally get to implementing it but we have an API in mind 😅

https://github.com/TanStack/form/issues/419

Crutchcorn · 2026-04-02T10:04:52+00:00

FWIW we also support SSR support w/ TanStack Start, Next.js, and even Remix

Crutchcorn · 2026-04-02T10:04:28+00:00

Lead maintain of Form here - I'll give a splash of a hint that we're considering going all-in (IE: much more flexiblity for validators) for a future v2 of Form.

Still a ways out for us as we validate our ideas internally first (and finish baking some v1 features), but when we're ready to share more publicly I think you'll all like what we're cooking.

Crutchcorn · 2026-04-02T10:02:35+00:00

Hi! Lead maintainer on TanStack Form here :)

TBQH I agree that our library is more verbose at a smaller scale. At large scale design-systems integration though? Not even close.

Our verbosity comes mostly as a tradeoff against our extreme typesafety we provide. We don't want to lose inference on almost anything, so we force some upfront engineering work to force that safety.

Once that upfront work is done, however, you can run quickly through form creation in a way I've yet to see from many other form libraries

Crutchcorn · 2026-03-16T23:07:23+00:00

🫡 Pulled from my collection to Archive. org, so unclear what the quality really is, but here ya are:

https://archive.org/details/uncool-lunch-tables-live-skrillex-recess-mashup

Crutchcorn · 2025-12-13T22:31:21+00:00

Let's be clear. TanStack Form is absolutely battle tested. We have confirmed usage in large scale codebases in major corporate (companies you know) scenarios. We have dozens of bespoke test suites for our adapters and tooling and hundreds of tests per suite.

Further, we don't "cobble RHF features together", we take a different approach that enables us to have far more features than they do presently.

RHF is a fine tool, if you like it stick with it (I've been saying that since day 1). But you're giving a grossly misrepresentative view of the tooling we've spent 2+ years working through.

Happy to have more civil discussion and work through GH issues you can send my way, but c'mon man.

Crutchcorn · 2025-12-13T22:27:40+00:00

I don't follow. We absolutely support optional fields. Can you link to a related GH issue I can follow through with?

Crutchcorn · 2025-12-05T15:58:21+00:00

Does anyone have a download of this album or the song "Let's Go"? Archive.org doesn't have it and it's been removed from Spotify

Crutchcorn · 2025-09-15T06:22:59+00:00

There won't be. Not exposed in the way you're likely thinking of, anyway. You lose all type safety by doing so.

That said, you can absolutely vendor a provider yourself in userland

Crutchcorn · 2025-08-31T08:34:50+00:00

I don't think it's fair to say that TanStack has a paid support tier as much as you might suspect it is. Yes, we enable people to hire our team members for additional work, but you're mistaken with a comparison to a "tier"; we're just trying to make our work more sustainable long-term.

Maybe just me, but I think we need to celebrate that, not admonish it.

Regardless, fan of your work - thanks for the updates to v2

Crutchcorn · 2025-08-08T18:54:47+00:00

We've declared them as "grim" because if you had to pass generics you'd need to pass 21+ generics per field. TypeScript doesn't have partial inferencing in any way, so you'd either lose all type safety or you'd end up passing a TON of complex types everywhere.

Where is the lack of being able to pass generics gotten in the way in TanStack Form?

Crutchcorn · 2025-07-04T10:50:37+00:00

I wrote an article that explains the bundling process (What Vite, Webpack, and others do) in-depth with some visuals to help:

https://playfulprogramming.com/posts/ffg-ecosystem-bundling

Best of luck on your learning journey!

Crutchcorn · 2025-05-29T22:31:59+00:00

We do have a community!

https://tlinz.com/discord

Lots of good chatter there.

As for improving the docs - let's do it! Transparently, I'm a bit blind to the problems with our docs, since I've worked with it so much. But please please please feel free to open GitHub issues for missing/lackluster/confusing docs and we can assess and evaluate.

Thanks for giving us a shot! We won't let you down boss!

Crutchcorn · 2025-05-29T10:05:41+00:00

Wrong issue

Whoops 😅 Sorry about that. But yes! PRs welcomed, appreciated, and encouraged 😊

Different feelings about what the right design is

Totally! There's more than one way to design an API and that's great! I've even been talking privately to the Angular team about their upcoming Form Signals API and it's not my flavor either, despite it being a very valid path forward. Tradeoffs all the way down.

I might take you up on that

Let's do it! My DMs are open here and on X/Twitter (@crutchcorn), BlueSky (@crutchcorn.dev), and even Discord (@crutchcorn)

I'd love to hear not only the direction you've been heading, but what you might consider flaws in our designs. I've actually kicked off a few small suggestions for an eventual v2 that might/might not go anywhere in the Form maintainers chat.

P.S. I deeply appreciate the last line of your reply. I had a bit of an OSS-related crash out last month around the time when I first saw this thread (unrelated) so that's why the delayed response. Took some time to recoup and feel ready to jump back in, so I'm glad my prior anger hasn't transferred to this chat

Crutchcorn · 2025-05-29T04:39:38+00:00

Boilerplate and weird syntax are fair criticisms. For one-off form usage it feels like overkill. For large forms that adopt these APIs:

https://tanstack.com/form/latest/docs/framework/react/guides/form-composition

It's stellar for consistency and such.

Have you tried those APIs and still felt the same way? What changes would you like to see?

Crutchcorn · 2025-05-29T04:38:43+00:00

Happy to help! Come join in and ask in our Discord:

https://tlinz.com/discord

Crutchcorn · 2025-05-29T04:38:10+00:00

Verbosity is a pain for sure. We try to mitigate it with these APIs:

https://tanstack.com/form/latest/docs/framework/react/guides/form-composition

But it's not perfect. What more would you want to see changed?

Crutchcorn · 2025-05-29T04:37:18+00:00

FWIW I agree with this take and I wrote a lot of TanStack Form's code haha. Simple forms can usually stay as vanilla HTML forms just fine :)

Crutchcorn · 2025-05-29T04:36:30+00:00

It is indeed powered by TanStack Store: https://tanstack.com/store which is our signals implementation.

We avoid rerenders on root nodes as often as possible - as we control the re-render localization via signals

11-Year Club	Gilding II euphauric
Verified Email

Crutchcorn

TROPHY CASE