FAQ

Does NotForm include UI components?

No. NotForm is headless. It renders a native <form> and passes state to your own markup or your component library. See Integrations.

Which validators work?

Any library that implements Standard Schema and produces an object schema. Zod, Valibot, and ArkType are common choices. NotForm has no validation rules of its own.

Do I need a schema?

Yes. schema is required. It is how NotForm types your values and how validation runs.

Can I use more than one form on a page?

Yes. Each useForm call creates an independent form with its own values, errors, and state.

Does it work with SSR and Nuxt?

Yes. NotForm creates its state during setup without needing browser APIs. Use @notform/nuxt for auto-imports.

Which Vue version is required?

Vue 3.5 or later.

Can the schema change at runtime?

Yes. Pass a ref or a getter as schema. See Validation.

Why is the form value a string when my schema outputs a number?

form.values holds the schema input, which is what the control edits. Your submit handler receives the output. See Schema input and output.

How do I validate on every keystroke?

Set validateOn: { input: true } on the field. See Validation.

How do I validate only on submit?

Disable blur and change validation and use lazy mode. See the "Validate on submit only" preset in Validation.

How do I show errors returned by my API?

Call form.setError({ message, path }). See Server errors.

How do I load saved data into a form?

Pass it as initialValues, or call form.reset(values) when it arrives. See Editing existing data.

How do I pass a form to a child component?

Type the prop as UseFormInstance<typeof schema>. See TypeScript.

Can I use it with my component library?

Yes. Map the control's value to field.model and its events to field.events. See Custom components, Nuxt UI and ShadcnVue.

Can I use NotForm with an AI coding assistant?

Yes. See Working with AI.