@octanejs/hook-form

React Hook Form for the octane renderer — the complete react-hook-form 7.81.0 source ported onto octane's hooks: performant, flexible forms with native-event validation, field arrays, schema resolvers, Controller/FormProvider, and SSR.

import { useForm } from '@octanejs/hook-form';

export function App() @{
	const {
		register,
		handleSubmit,
		formState: { errors },
	} = useForm({ mode: 'onChange' });

	<form onSubmit={handleSubmit((data) => console.log(data))}>
		<input {...register('email', { required: 'required' })} />
		@if (errors.email) {
			<span role="alert">{errors.email.message as string}</span>
		}
		<button>{'Submit'}</button>
	</form>
}

The one API difference: onInput

Octane has native, delegated events — no synthetic event layer. The per-keystroke text event on the platform is input (native change fires on blur/commit), so the handler upstream calls onChange is exposed as onInput:

• register(name) returns { name, ref, onInput, onBlur } (upstream: onChange). {...register('x')} spreads work unchanged.
• useController's field is { value, name, ref, onInput, onBlur, … }. field.onInput doubles as the programmatic setter (accepts an event or a raw value), exactly like upstream's field.onChange.
• mode: 'onChange' / reValidateMode: 'onChange' option VALUES are unchanged — validation still runs per keystroke (driven by native input).
• Register OPTIONS keep their upstream names: register('x', { onChange, onBlur }) callbacks are invoked as before.

The remaining adapted behavior — validation modes, formState proxy subscriptions, useFieldArray, useWatch/Watch, FormStateSubscribe, reset/setValue/ trigger semantics, SSR via octane/server — matches upstream behavior; the automated parity checks run all 1,193 tests and eight snapshots unchanged against the pinned React package as a pristine baseline. The Octane port separately runs its byte-locked adapted DOM and server suites without title filters. Their manifests record 1,187 collected entries representing 1,178 unique file/full-name identities and require every entry to execute and pass. The nine duplicate entries are repeated titles within the DOM inventory; the server inventory is disjoint. The structured divergence ledger in audit/react-parity.json records the native-event, scheduling, render-bailout, and test-flush differences, including consumer impact and migration guidance. Differential tests also assert byte-identical DOM against the real react-hook-form. See UPSTREAM.md for the pin, source inventory, export crosswalk, and test dispositions. The root Vitest project declares upstream and differential files as react-parity execution group ownership; the generic sharded config derives the remaining local conformance suite according to the React parity test-execution contract.

License

MIT — contains source derived from react-hook-form (MIT, © Beier (Bill) Luo), adapted for octane.

Status

Current scope, known divergences, and verification status are tracked in the generated bindings status table, sourced from this package's status.json.