I'll create a single email input field with validation that demonstrates all the different variants of our new FormInput component. We'll use a simple email validation and add a specific check for Gmail accounts.

These changes create a single email input field that demonstrates all the variants of our FormInput component:

1. Default state: When the input is empty.
2. Focus state: When the input is focused (this is handled by the CSS).
3. Hover state: When a valid email is entered (not Gmail).
4. Error state: When an invalid email is entered or a Gmail address is used.
5. Success state: When a valid non-Gmail email is entered.

The component now:

• Validates the email as the user types.
• Shows an error for invalid email formats.
• Shows a specific error for Gmail accounts.
• Displays a green check mark for valid non-Gmail emails.
• Uses different border colors and shadows for error and success states.

This implementation allows you to see all the different states of the input in action. You can easily extend this further by adding more complex validation rules or additional input types as needed.

Certainly, I'll remove the success state and simplify our component to focus on the default, hover, and error states for the email input field.

Let's update our components to remove the success state:

These changes accomplish the following:

1. Removed the success state from the FormInput component.
2. Simplified the inputVariants to only include default and error variants.
3. Removed the success icon and related logic from the FormInput component.
4. Updated the EmailForm component to use only the default, hover, and error states.
5. Maintained the email validation logic, including checks for valid email format and Gmail accounts.

The component now has three main states:

• Default: When the input is empty or focused.
• Hover: When a valid non-Gmail email is entered (the input will have a hover effect).
• Error: When an invalid email is entered or a Gmail address is used.

This simplified version still demonstrates all the required functionality while adhering to your request to remove the success state.