❌

Reading view

Where do you store state in a multi-step React form: URL params, context, Zustand, or the form library?

Building a 5-step wizard with React Hook Form and Zod. I keep the step in the URL and drafts in a small store. What has held up in production for you, and how do you handle early-step changes that invalidate later steps?

submitted by /u/Big_Muffin8280 to r/reactjs
[link] [comments]
  •  

CupertinoUI: macOS-style components you install with the shadcn CLI

I built CupertinoUI, a macOS-style component registry for React and shadcn/ui.

It includes controls, menus, dialogs and windows, with CSS-variable theming and light/dark appearance. Components are copied into your project through the shadcn CLI so you can edit the source.

The core components are free under MIT. There are also paid Pro components and complete app-style blocks.

Try the interactive desktop: https://www.cupertino-ui.com/demo
Browse the components: https://www.cupertino-ui.com/docs/components

submitted by /u/Dependent_Common2109 to r/reactjs
[link] [comments]
  •  

How do you keep forms sane in large React apps?

Forms are still where most of my React bugs live: validation that disagrees with the backend, async defaults, conditional fields.

My current stack is React Hook Form with Zod schemas shared with the NestJS backend. It mostly works, but complex multi-step forms still get messy.

What's your setup? Anyone moved to server actions for most forms and been happy with it?

submitted by /u/No-Task-4473 to r/reactjs
[link] [comments]
  •  
❌