useActionState를 활용한 필드별 검증 오류
액션에서 구조화된 검증 결과를 반환하고 필드별 오류 메시지를 인라인으로 렌더링하는 방법을 배웁니다.
useActionState를 활용한 필드별 검증 오류은(는) CoddyKit의 무료 Next.js 15 Fullstack (App Router + Server Actions) 강의입니다. 이것은 4개 중 3번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Next.js 15 Fullstack (App Router + Server Actions) 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Next.js 15 Fullstack (App Router + Server Actions) 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Why Field-Level Errors?
When a form fails validation, users need to know exactly which field is wrong and why. A single banner saying "Something went wrong" forces them to guess.
In Next.js 15, Server Actions paired with useActionState let you return a structured result from the server and render an inline error right beneath each input.
emailis invalid → show the error under the email fieldpasswordis too short → show it under the password field
This lesson shows how to return that structure and render it cleanly.
Shaping the Action State
Start by deciding the shape of what your action returns. A good pattern keeps per-field errors in an errors map keyed by field name, where each value is an array of messages.
Defining a TypeScript type makes the contract explicit for both the action and the component.
export type FieldErrors = {
email?: string[];
password?: string[];
};
export type SignupState = {
errors?: FieldErrors;
// value the user typed, so we can re-fill the form
values?: { email?: string };
// a top-level message for non-field errors
message?: string;
};
export const initialState: SignupState = {};Validating with Zod in the Action
A schema library like Zod gives you both validation and a ready-made error structure. Call safeParse so failures don't throw — instead you inspect the result.
flatten().fieldErrors returns exactly the { field: string[] } shape we designed, so it maps directly onto our state.
import { z } from 'zod';
const SignupSchema = z.object({
email: z.string().email('Enter a valid email'),
password: z.string().min(8, 'At least 8 characters'),
});
const result = SignupSchema.safeParse({
email: 'not-an-email',
password: '123',
});
if (!result.success) {
// { email: ['Enter a valid email'], password: ['At least 8 characters'] }
console.log(result.error.flatten().fieldErrors);
}The Server Action Signature
An action used with useActionState receives two arguments: the previous state and the submitted FormData. It must return the next state.
Mark the file or function with 'use server'. Read values with formData.get(...), validate, and return errors instead of throwing.
'use server';
import { z } from 'zod';
import type { SignupState } from './state';
const SignupSchema = z.object({
email: z.string().email('Enter a valid email'),
password: z.string().min(8, 'At least 8 characters'),
});
export async function signup(
prevState: SignupState,
formData: FormData,
): Promise<SignupState> {
const email = String(formData.get('email') ?? '');
const password = String(formData.get('password') ?? '');
const parsed = SignupSchema.safeParse({ email, password });
if (!parsed.success) {
return {
errors: parsed.error.flatten().fieldErrors,
values: { email }, // keep email, never echo the password
};
}
// ...persist the user here...
return { message: 'Account created' };
}Wiring useActionState
In your client component, call useActionState(action, initialState). It returns a tuple:
state— the latest value your action returnedformAction— pass this to the form'sactionpropisPending— true while the action runs (great for disabling the button)
Remember the 'use client' directive — hooks only run in client components.
'use client';
import { useActionState } from 'react';
import { signup } from './actions';
import { initialState } from './state';
export function SignupForm() {
const [state, formAction, isPending] = useActionState(
signup,
initialState,
);
return (
<form action={formAction}>
{/* inputs go here */}
<button disabled={isPending}>
{isPending ? 'Creating...' : 'Sign up'}
</button>
</form>
);
}Rendering an Inline Error
To show a field error, read it from state.errors?.fieldName. Because each field holds a string array, render the first message (or map over all of them).
Use optional chaining so the very first render — when errors is undefined — doesn't crash.
<div>
<label htmlFor="email">Email</label>
<input
id="email"
name="email"
type="email"
defaultValue={state.values?.email}
/>
{state.errors?.email && (
<p className="error">{state.errors.email[0]}</p>
)}
</div>Accessibility: Linking Errors to Inputs
Screen readers should announce the error and tie it to the field. Two attributes do the heavy lifting:
aria-invalid— settruewhen the field has an erroraria-describedby— point to the id of the error element
Give the error element a stable id and a polite live region so updates are read aloud.
<input
id="email"
name="email"
type="email"
defaultValue={state.values?.email}
aria-invalid={!!state.errors?.email}
aria-describedby="email-error"
/>
{state.errors?.email && (
<p id="email-error" className="error" aria-live="polite">
{state.errors.email[0]}
</p>
)}Preserving User Input
Because the form re-renders from server state, an uncontrolled input would lose what the user typed. Return the safe values from the action and feed them back with defaultValue.
Never echo passwords back to the client. Only return non-sensitive fields like email so the user doesn't retype everything after a validation error.
// in the action, on failure:
return {
errors: parsed.error.flatten().fieldErrors,
values: { email }, // safe to round-trip
// password is intentionally omitted
};
// in the component:
<input name="email" defaultValue={state.values?.email} />
<input name="password" type="password" /> {/* always blank */}A Pure Validation Helper You Can Test
Validation logic doesn't need Next.js to be correct. Extract it into a pure function that takes plain values and returns the same { field: string[] } error map. This is trivially unit-testable and runnable on any judge.
type FieldErrors = { email?: string[]; password?: string[] };
function validateSignup(email: string, password: string): FieldErrors {
const errors: FieldErrors = {};
const emailOk = /^[^@\s]+@[^@\s]+\.[^@\s]+$/.test(email);
if (!emailOk) errors.email = ['Enter a valid email'];
if (password.length < 8) errors.password = ['At least 8 characters'];
return errors;
}
const e1 = validateSignup('bad', '123');
console.log(e1); // { email: [...], password: [...] }
const e2 = validateSignup('a@b.co', 'longenough');
console.log(Object.keys(e2).length === 0); // true
console.log(JSON.stringify(validateSignup('x@y.com', 'short')));Multiple Errors per Field
A single field can fail several rules at once (empty, too short, wrong format). Since each entry is an array, you can render every message as a list.
Zod naturally accumulates multiple issues per field, so fieldErrors.password may contain more than one string.
{state.errors?.password && (
<ul className="error-list">
{state.errors.password.map((msg) => (
<li key={msg}>{msg}</li>
))}
</ul>
)}Top-Level vs Field Errors
Not every failure belongs to a field. A duplicate-email conflict from the database, or a generic server fault, is a form-level message.
Keep both channels in your state: errors for per-field issues and message for the whole form. Render the top-level message above the fields so it isn't missed.
// in the action, after a successful parse:
try {
await createUser(email, password);
} catch (err) {
if (isUniqueViolation(err)) {
return { errors: { email: ['Email already in use'] } };
}
return { message: 'Something went wrong. Please try again.' };
}
// in the component, above the fields:
{state.message && <p role="alert">{state.message}</p>}Quick Check
Test your understanding of the action contract used by useActionState.
Recap
You can now build field-level validation with Server Actions and useActionState:
- Shape the state with an
errorsmap of{ field: string[] }, plus optionalvaluesand a top-levelmessage. - Validate in the action with
safeParseand returnflatten().fieldErrors— return, never throw. - Wire the hook with
useActionState(action, initialState)and passformActionto the form; useisPendingfor the button. - Render inline from
state.errors?.field, witharia-invalidandaria-describedbyfor accessibility. - Preserve input via
defaultValue, but never echo passwords. - Separate channels: per-field
errorsvs form-widemessage.
자주 묻는 질문
“useActionState를 활용한 필드별 검증 오류” 강의는 무료인가요?
네 — “useActionState를 활용한 필드별 검증 오류” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Next.js 15 Fullstack (App Router + Server Actions) 강의 전체를 잠금 해제할 수 있습니다. Next.js 15 Fullstack (App Router + Server Actions) 강의에는 총 4개의 강의가 포함되어 있습니다.
“useActionState를 활용한 필드별 검증 오류”에서 뭘 배우나요?
액션에서 구조화된 검증 결과를 반환하고 필드별 오류 메시지를 인라인으로 렌더링하는 방법을 배웁니다. 브라우저에서 직접 실행하는 실습 코드로 Next.js 15 Fullstack (App Router + Server Actions)을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
Next.js 15 Fullstack (App Router + Server Actions)을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 Next.js 15 Fullstack (App Router + Server Actions)은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 3번째 강의입니다.
“useActionState를 활용한 필드별 검증 오류” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 Next.js 15 Fullstack (App Router + Server Actions) 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 Next.js 15 Fullstack (App Router + Server Actions) 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- form Action 속성을 활용한 점진적 향상
- useFormStatus를 활용한 대기 및 로딩 상태
- useActionState를 활용한 필드별 검증 오류
- useOptimistic으로 즉각적인 피드백 제공