🦋 Ben retweeted
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 longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit.
2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: <FormKit type="any-input-type-here"> and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”.
3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state.
4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input:
<FormKit
type="text"
name="email"
label="Email address"
help="How should we get ahold of you?"
validation="required|email"
/>
Colocation dramatically improves the efficacy of coding agents.
5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to.
6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa.
7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way.
Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is.
With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents.
➡️ formkit.com
🦋 Ben retweeted
PSA: If you see two verified "Vue - Official" extensions in VSCode, pick the one with the more recent version.
This is a bug in VSCode marketplace that we have no control over until it is fixed.
More context github.com/vuejs/language-to…
Replying to @evanyou
This seems to lead many users to install the 2.0.10 version because it shows more downloads - but the latest is already 2.0.14.
🦋 Ben retweeted
It feels like CSS has come such a long way. Nearly all of the major pain points that developers have faced for decades are either resolved or well on their way. This is a good thing!
Of course the web is never done, but it does feel like we've hit an infection point.
🦋 Ben retweeted
Big release for @firefox and an exciting day for web developers! 🎉🎉🎉
:has() is here!!! 🎉🪩🥳
:has, text-indent: hanging, text-wrap: balance, iframe lazy loading, … @Firefox 121 is released today with lots of presents for web developers 🥳
mozilla.org/en-US/firefox/12…
🦋 Ben retweeted
Welcome 💿 to the ⚡️party!
Today we are excited to share our new Vite plugin available in Remix v2.2.0!
Vite’s lightning fast DX ⚡️ means
10x faster HMR
5x faster HDR
We are also happy to announce that Remix is officially sponsoring Vite!
Read more about our announcement here
remix.run/blog/remix-heart-v…
🦋 Ben retweeted
Nuxt Studio is out of beta and open to everyone ✨
nuxt.studio
🦋 Ben retweeted
Like @vuejs? Happy to share @lydiahallie and I are teaming up with @djirdehh (author of Fullstack Vue) to bring a free Vue design patterns guide to Patterns.dev 🥳
Excited to share more updates soon. Stay tuned!
🦋 Ben retweeted
If you're wondering what's the deal with Signals and how they are related to Vue refs, I wrote something up in the Vue docs: vuejs.org/guide/extras/react…
🦋 Ben retweeted
🚀 We just released Tailwind CSS v3.2 and it's huge!
🧁 Multi-config support with `@config`
🍭 Max-width and dynamic breakpoints
🍫 ARIA variants
🍪 Data attribute variants
🍬 `@supports` variants
🍦 Nested groups
🍰 Container queries
…and more 🤤
tailwindcss.com/blog/tailwin…
🦋 Ben retweeted
Vuejs Amsterdam 9-10 Feb 2023 🔥 CFP and Blind Tickets now available 🥳
🤩 What to expect? Full video now: vuejs.amsterdam
Join World's Most Special and Largest Vue Conference
👉 Core Team, Authors, Afterparties and more!
🚨 Lowest priced blind tickets NOW for sale
🦋 Ben retweeted
Are there any patterns / plugins for Vue / Vite to detect when there is a new version of the application available?
I have some ideas but no point reinventing the wheel if it exists.
🦋 Ben retweeted
I can say with absolute certainty that if I started Tailwind CSS over from scratch, there would be no `@apply` 😬
The behavior is outrageously complicated, everyone struggles to build the right mental model of what it's supposed to do, and it encourages bad CSS architecture.
🦋 Ben retweeted
We first thought that Astro islands & partial hydration would be impossible in MDX, but @n_moore recently cracked it.
You can now author MDX in Astro and still use components from any framework including non-JSX frameworks Vue and Svelte!






















