Input
FormsCollects a single-line value through a native input with optional composed affixes and clearing controls.
Try it
Add to your project
npx shadcn@latest add https://luv-jeri.github.io/cojeev-ui/r/input.jsonThe command includes the component’s shared dependencies. Your project keeps editable source files.
Include the complete example
This example also composes icon, label, typography. Install its parts together:
npx shadcn@latest add https://luv-jeri.github.io/cojeev-ui/r/input.json https://luv-jeri.github.io/cojeev-ui/r/icon.json https://luv-jeri.github.io/cojeev-ui/r/label.json https://luv-jeri.github.io/cojeev-ui/r/typography.jsonUsing input
Pass native type, name, value, and onChange props to match the data you need.
Use InputWrapper and InputControl for addons, and connect InputClear onClear to the input value.
API
Compose the exported parts below. The prop types are read from the React source during the registry build.
Native element or underlying primitive props are inherited where declared, including accessible labels, event handlers and refs.
InputProps
| Prop | Type | Required |
|---|---|---|
variant | "default" | "cream" | null | undefined | No |
size | "default" | "sm" | null | undefined | No |
nativeSize | number | No |
InputWrapperProps
| Prop | Type | Required |
|---|---|---|
variant | "default" | "cream" | null | undefined | No |
size | "default" | "sm" | null | undefined | No |
ref | React.Ref<HTMLElement> | No |
as | "div" | "label" | No |
InputControlProps
Accepts the native or primitive props declared by its exported TypeScript type.
InputAddonProps
Accepts the native or primitive props declared by its exported TypeScript type.
InputAffixProps
Accepts the native or primitive props declared by its exported TypeScript type.
InputClearProps
| Prop | Type | Required |
|---|---|---|
onClear | () => void | No |
Accessibility
Associate a visible label with the input and connect instructions or errors using aria-describedby.
Use the native required and disabled attributes for those behaviors; visual variants alone do not enforce validation.
States and appearance
For conditional content, keep a MotionPresence boundary around keyed MotionSurface children. The shared entrance and exit states work with native primitives and respect your motion preference.
Try pointer and keyboard interaction, and switch the appearance control in the navigation to compare light and dark mode. Motion respects reduced motion preferences.