Entrypoints

@ilokesto/form has one framework-neutral root entrypoint and four adapter entrypoints. Import CreateForm and all core public types from the root, including CreateFormOptions, FieldPathInput, FieldPathValue, FieldSchemaOptions, FieldState, Form, FormArray, FormError, FormState, ResetOptions, SetValueOptions, StandardSchemaV1, and ValidationTrigger. Import framework helpers from @ilokesto/form/react, @ilokesto/form/vue, @ilokesto/form/solid, or @ilokesto/form/svelte.

import { CreateForm, type FieldState, type FormError } from '@ilokesto/form';
import { useForm as useReactForm } from '@ilokesto/form/react';
import { useForm as useVueForm } from '@ilokesto/form/vue';
import { useForm as useSolidForm } from '@ilokesto/form/solid';
import { useForm as useSvelteForm } from '@ilokesto/form/svelte';

The root entrypoint stays free of framework peers. The adapter subpaths declare optional peer expectations through the package: React, Vue, Solid, and Svelte applications should install their own renderer. Keeping imports explicit also prevents accidentally documenting Svelte as if it had React-like hooks. Svelte exposes an action-based register plus useField, useFormState, and handleSubmit; it does not expose useRegister.

Practical guidance

Keep this page near the source when you build abstractions. The reference describes what the package exposes, while guides show one way to compose those pieces. If a helper hides FieldPathInput, validation triggers, or array rebasing, document that helper with the same precision so future maintainers know whether strings, tuples, or stable keys are expected.