Server Actions yaiku fungsi async sing mlaku ing server nanging bisa ditaleni langsung saka component mu (kalebu saka form lan event handler) — ngidini pikeun laku mutasi (nggawe/ngobah/busak) tanpa kudu nggawa endpoint API dhewe-dhewe. Sampeyan nandhai dheweke nganggo direttif "use server".
;
{ revalidatePath } ;
() {
title = formData.() ;
db..({ : { title } });
();
}
// app/todos/page.tsx — wire the action straight to a form
import { createTodo } from "./actions";
export default function Page() {
return (
<form action={createTodo}> {/* no onSubmit, no fetch, no /api route */}
<input name="title" />
<button>Add</button>
</form>
);
}
Aktribut action form nunjuk menyang Server Action. Nalika disubmit, Next.js ngirim FormData menyang server, njalanake fungsi kana, lan bisa revalidasi kaca sing kena pengaruh — kabeh tanpa rute API lan tanpa kode fetch sisi klien.
"use client";
import { createTodo } from "./actions";
export function AddButton() {
return <button onClick={() => createTodo(/* ... */)}>Add</button>;
}
route.ts lan fetch klien.revalidatePath/revalidateTag nyegari data sing dicache sawise mutasi.⚠️ Server Actions are PUBLIC endpoints under the hood — always validate input and
check authorization inside them, exactly as you would a real API route.
Server Actions ngurangi stack mutasi biasane (rute API + fetch klien + panganan status) dadi fungsi server tunggal sing sampeyan taleni langsung — jawaban App Router kanggo form lan owah-owahan data.
Kulah boilerplate, gawe progressive enhancement, lan integrasine karo cache/revalidasi, nanging (kaya endpoint apa wae) mbutuhaké validasi lan pemeriksaan auth ing sajrone.
Pustaka pitakon wawancara IT kanthi jawaban rinci — saka Junior nganti Senior.
Nyumbang