FormKit @FormKit

A free & open source Vue form building framework that simplifies form structure, generation, validation, accessibility, error handling, and more. formkit.com Charlottesville, VA Joined December 2020

Tweets

220
Followers

2K
Following

254
Likes

1K

FormKit @FormKit

3 months ago

@ahvsfporra Not in the roadmap currently

0 0 1 7 0

View Details

FormKit @FormKit

3 months ago

FormKit is now available for React! Been wanting to do this for a while.

Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no

7 6 113 12K 71

1 0 10 531 3

View Details

FormKit @FormKit

4 months ago

A/B test different coding agents.

Justin Schroeder @jpschroeder

4 months ago

dmux just shipped support for 11 coding agents including A/B testing for any/all of them. Now supports: @claudeai, @cline, @Alibaba_Qwen, @opencode, @OpenAI, @AmpCode, @charmcli, @cursor_ai, @github copilot, @geminicli, pi Also new ui & merge diffs ➡️dmux.ai

14 15 103 19K 87

0 0 2 310 0

View Details

FormKit @FormKit

4 months ago

New productivity level unlocked.

Justin Schroeder @jpschroeder

4 months ago

We're open sourcing dmux. Our internal tool for running Codex and Claude Code swarms. - tmux + worktrees + claude/codex/opencode - hooks for worktree automation - a/b claude vs codex - manage worktrees - multi-project per session ...more. ➡️ dmux.ai

131 270 3K 328K 5K

0 0 5 560 1

View Details

Justin Schroeder @jpschroeder

6 months ago

Launch day for @FormKit! - Beautiful new docs site - Themes updated to Tailwind 4 - Improved @nuxt_js 4 support - lots of bug fixes - Lots and lots of ecosystem maintenance Go checkout the new website, oh yeah, we finally put some of FormKit’s users on the website 👀

4 2 30 2K 1

View Details

FormKit @FormKit

7 months ago

New features and bug fixes coming soon...👀

1 0 4 589 0

View Details

Lee Martin @leemartin

9 months ago

@mockvideo @boniver @instagram @nuxt_js @Netlify @contentful @uppy_io @transloadit @goserverless Shout out to @formkit for once again providing the excellent inputs that make these apps possible and a joy to maintain.

1 1 2 574 0

View Details

Justin Schroeder @jpschroeder

2 years ago

🎃 Available for the next 2 days: FormKit Pro Unlimited: 🤫 No telemetry for life 📈 Unlimited projects for life ♻️ Free updates for life 1️⃣ One payment for life ($3,495) ❤️ My personal gratitude for life 🔗 👇👇👇

1 5 24 4K 3

View Details

Justin Schroeder @jpschroeder

2 years ago

📣 Announcing: KickStart! A next-generation form builder from the @FormKit team. Going live...now 👀 Generate a form, edit it with manual controls or AI prompts, then copy and paste @vuejs components or schema into your project. 🔗👇

9 29 228 41K 106

View Details

FormKit @FormKit

2 years ago

And make sure you're importing only the Pro Inputs you need in your installation: import { createProPlugin, repeater, dropdown } from @formkit/pro

0 0 5 1K 0

View Details

FormKit @FormKit

2 years ago

We've greatly improved tree shaking in FormKit Pro. Update to v0.125.2 or later to get the benefits.

1 0 8 2K 0

View Details

FormKit @FormKit

2 years ago

@IsraelOrtuno Great to hear. We may have something that helps with this in the near future.

1 0 1 45 0

View Details

Justin Schroeder @jpschroeder

2 years ago

🚨🚨 New FormKit Pro input released today...🥁... The currency input! 💰💸💵💶💷💴🪙 🔗👇

4 5 49 5K 4

View Details

Justin Schroeder @jpschroeder

2 years ago

Coming soon to @FormKit — built in icon loaders! - Eva - FormKit - Hero - Ion - Lucide - Material Anyone other open source icons we should add?

11 2 37 5K 3

View Details

FormKit @FormKit

2 years ago

@ivano_da_gioia Oh no! was this adding it to an existing nuxt 3 app? We’ll take a look and make sure there aren’t any known issues there.

0 0 0 27 0

View Details

Luan Nguyen @luanguyen

2 years ago

.@FormKit is 2 stars away from 4,000. Push us over 🙏! github.com/formkit/formkit Also thankful for our other open source projects getting love: - AutoAnimate: 11,467 - Tempo: 1,947 - Drag and Drop: 786

2 1 14 1K 2

View Details

FormKit @FormKit

2 years ago

We expected "Integration w/ UI libs" to win. But were surprised that "Form builder + publish" was a close 2nd. Thanks for voting!

FormKit @FormKit

2 years ago

Which FormKit feature would you like to see next? Reply with other feature requests if not in the poll.

1 1 7 4K 1

0 0 6 2K 0

View Details

Justin Schroeder @jpschroeder

2 years ago

FormKit 1.6 is out today! 🧩 New composables like useFormKitContext ⚙️ Improved TypeScript support 📙 Added library prop for FormKit components 🐛 Deez bugs fixed: formkit.com/changelog Excited about the composables! They let you build complex forms even more fluently ❤️

1 4 45 3K 3

View Details

Justin Schroeder @jpschroeder

2 years ago

Rolldown might be the most important web project of the next 5-10 years. I thought it might be helpful to explain why: The landscape: Rollup is the best and most comprehensive bundler to date. It was ahead of its time, pioneering key concepts like tree shaking (🙏 @Rich_Harris & @lukastaegert) and still hasn’t been matched in this regard. When @evanyou introduced @vite_js — Rollup was a cornerstone of the build process. Vite plugins are (for the most part) Rollup plugins. It didn’t take long for Vite to become the standard development and build environment for nearly every major meta framework: @nuxt_js, @solid_js start, @sveltejs kit, @remix_run, @angular cli, etc. (basically everything except Next). Rollup is still the underpinning of all of these. It has gone from being a way to bundle your library before publishing on npm to the backbone of how the modern web is being written. The problem: We find ourselves in a world where Rollup has been pressed into service building nearly every byte on the web — something it wasn’t originally intended to do — and its performance (really JavaScript’s performance) could be improved. esbuild (🙏 @evanwallace), a bundler written in Go, showed the world just how much faster a "native" bundler can be, but esbuild was not Rollup compatible and had its fair share of shortcomings as well (no TypeScript, limited tree shaking, etc.). @vite_js uses esbuild and Rollup to get the best of both worlds, but here lies another problem: parsing. Different build tools use different AST trees, and each of these must parse the code to derive the AST. Also, many plugins for Rollup/Vite perform their own parsing. Wouldn’t it be incredible if the parsing was done a single time and a single AST tree could be used by all layers of the build stack? @evanyou said recently that @vite_js often has to parse the same TS file at least 5 times at various levels in the stack. Clearly this could be better. The solution: The @rolldown_rs project is attempting to (eventually) solve all of these problems. First, it is written in Rust, one of the fastest languages out there — generally even faster than Go (i.e., esbuild) due to Rust not using garbage collection. In some applications, this doesn’t matter much, but in the context of parsing and compiling, this is a massive benefit (oh the irony that Rust itself is the world’s slowest compiler 😂). Rolldown isn’t just attempting to be fast though, it is also attempting to be API compatible with Rollup. This would be a monumental accomplishment (the Rollup API is not for the faint of heart). If successful, the @vite_js team could swap out the engine inside Vite while the plane is flying and we wouldn’t notice anything except we arrived at our destination much earlier. Finally — and perhaps most ambitiously — a standard singular parse. Perhaps this is a bit further down the road, but because Vite is so prevalent and because Rolldown uses OXC (🙏 @boshen_c) for parsing, we could end up in a world that standardizes around a single parse and AST tree. The performance improvements we could see in our development environment and build times would be tremendous. If successful, Rolldown will be responsible for transforming nearly every byte of web code — no matter what framework you use (happy to share my thoughts on what it means for Next some other time). Thanks: Finally, thanks to the @vite_js team, and everyone working on @rolldown (@_hyf0, @_h_ana___, @evanyou)! I am in no way affiliated with these fine engineers, just a mere plebe building on the backs of these giants.