FormKit

@ahvsfporra Not in the roadmap currently

@FormKit What about angular

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

A/B test different coding agents.

New productivity level unlocked.

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 👀

New features and bug fixes coming soon...👀

@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.

🎃 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 🔗 👇👇👇

📣 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. 🔗👇

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

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

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

@FormKit Custom Tailwind at the moment but I have other projects where I had to map Nuxt UI components too

Hey @FormKit... That theme builder thing is just 🔥

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

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

@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.

@FormKit I tried to install your product in Nuxt 3 app, a disastrous install process experience. It does not work out of the box :( Where is in the docs this part how to set?!? [vite-node] [ERR_LOAD_URL] @formkit/themes

.@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

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

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 ❤️

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.