React Aria is now available in shadcn/ui.
Use `--base aria` or choose React Aria in shadcn/create.
All components, docs, CLI, styles and skills have been updated for React Aria Components.
Shoutout to @devongovett who did most of the work behind this release.
@KentonVarda This is my biggest gripe with AI code reviews today. There becomes a point where it’s just false-ish positives, and if you don’t filter those out, you get worse code as a result.
Introducing Foil Shaders
A Metal port of Paper Shaders for SwiftUI.
Includes:
- All 29 Shaders + Full API Parity
- Visual Parity Test Suite
- Mac app for previewing shaders and copying code snippets
Paper Shaders: now fully open source and FREE
Yes, you can make a: plugin, tool, template, site, app, library. Resell it. Make a Figma plugin. It's already code. Go for it!
We're pushing shaders forward. New Paper Shaders on the way.
React Aria Components v1.19.0 is out! ✨
Autocomplete now supports inline completions (e.g. mentions), and a new Popover API enables positioning relative to the cursor.
Also, text inputs can now be nested inside GridList and Tree without interfering with arrow key navigation!
Strict and principled design systems (with component libraries) are more important now than ever. They’re like a slop-filter for frontend.
Models have been RL’ed through a stack of filters:
Valid syntax
↓
Valid types
↓
Valid lint
↓
Valid UI (renders to spec)
Valid UI is a massive range, and it also happens to be what end-users see.
You need to supplement your own definition of “valid UI” at inference time. Design systems are the easiest way to do that, and luckily designers and engineers have been working on them for a while.