EmailInput
v1.0.6Updated 27 Aug 2026Validated email field with leading mail icon, trailing status pill, RFC 5322 regex, optional domain allowlist / blocklist, Levenshtein typo suggestions against 17 common providers ("Did you mean gmail.com?"), and server-
Preview
Live · 10 stories▸Why this is recommendedformemailvalidationtypo+4
The default, out-of-the-box EmailInput.
- ✓Signup forms
- ✓Work-email-only company signups
- ✓Disposable-inbox blocking
- ✓Email change flows
- RFC 5322 simplified regex validation
- Domain allowlist + blocklist
- Levenshtein typo suggestions against 17 common providers
- Server-side error injection
- validateOn: on-blur (default) / on-change / on-submit
- onValidityChange callback
- i18n: labels prop overrides the typo-suggestion chip strings; validation messages overridable via errorMessages
- ✕Free-text fields (use Input)
- ✕Multi-recipient inputs (use TagInput)
Install
Ask your agent, or call the MCP tool directly. The resolved bundle is written into your project.
Usage
Tick variants in the left menu — each adds a tab with that variant’s real story source, the same code the preview above renders.
Props
valueControlled value
—onValueChangeValue change callback
—onValidityChangeValidity + error[] callback
—allowedDomainsDomain allowlist
—blockedDomainsDomain blocklist (throwaway providers)
—suggestCorrectionsShow "Did you mean…" typo fixes
—validateOnValidation timing
—serverErrorForced server-side error
—requiredRequired field
—labelsOverride the built-in UI strings — the "Did you mean {suggestion}?" typo chip and its Apply action (i18n). Merged over DEFAULT_EMAIL_INPUT_LABELS; validation messages stay on errorMessages.
—