Fullstack with Nuxt
Sebagai Vue & Nuxt enthusiast wkwk, akhirnya my framework favorit bisa fullstack juga. Biasanya kalau fullstack, lari ke Laravel, Codeigniter, atau pernah juga Express, dan sekarang lagi nyobain pakai Golang sebagai Backend nya. Nuxt-nya sendiri cuma kebagian frontend tok. Nuxt sekarang ternyata bisa jadi Fullstack, dengan menggunakan NuxtHub.
NuxtHub
NuxtHub adalah platform backend full-stack yang dibangun langsung di atas ekosistem Nuxt untuk menyederhanakan pembuatan aplikasi web modern tanpa terikat pada satu penyedia infrastruktur (cloud vendor lock-in).
Arsitekturnya memanfaatkan fondasi dasar Nuxt, khususnya Nitro (server engine), unstorage (layer penyimpanan universal), dan db0 (layer database agnostic). Berkat pendekatan ini, kode backend yang ditulis di NuxtHub dapat berjalan di berbagai lingkungan cloud seperti Cloudflare, Vercel, Netlify, AWS, hingga server mandiri (self-hosted) tanpa perlu mengubah logika aplikasi.
Fitur Utama
- SQL Database
Menyediakan integrasi database relasional bawaan (berbasis db0). Pengembang bisa melakukan query, migrasi schema, dan manipulasi data langsung dari fungsi server Nuxt tanpa setup konektor database yang rumit.
- Blob Storage
Penyimpanan objek untuk aset media seperti gambar, video, atau dokumen. Fitur ini mempermudah proses unggah (upload) dan penyajian media secara otomatis lewat API seragam.
- Cache & Key-Value System
Sistem caching berkinerja tinggi yang dibangun dengan unstorage. Fitur ini digunakan untuk menyimpan sesi pengguna, mempercepat pemuatan API route, render halaman Nuxt, atau menyimpan data sementara secara efisien.
A. Setup Project
- Init Project
npx nuxi@latest init FullstackNuxtHubcd FullstackNuxtHub
npm install2. Add & Config NuxtHub
npx nuxi module add hubConfig optionsnuxt.config.ts :
export default defineNuxtConfig({
modules: ['@nuxthub/core'],
hub: {
// NuxtHub options
}
})3. Setup Nuxt SQL Database
NuxtHub menyediakan integrasi database SQL berbasis Drizzle ORM untuk Nuxt. Fitur ini mendukung PostgreSQL, MySQL, dan SQLite dengan kemampuan smart driver detection dan migrasi otomatis saat build.
//PostgresSQL
pnpm install drizzle-orm drizzle-kit postgres @electric-sql/pglite
//MySQL
pnpm add drizzle-orm drizzle-kit mysql2
//SQLLite
pnpm add drizzle-orm drizzle-kit @libsql/clientAktifkan opsi db pada nuxt.config.ts:
export default defineNuxtConfig({
modules: ['@nuxthub/core'],
hub: {
db: 'postgresql' // Pilihan: 'postgresql' | 'mysql' | 'sqlite'
}
})NuxtHub secara otomatis mendeteksi koneksi database menggunakan environment variables:
- Lokal (tanpa env variable): Otomatis menggunakan
PGlite(embedded PostgreSQL) atau file SQLite lokal di.data/db/sqlite.db. - Production: Otomatis membaca
DATABASE_URLatauPOSTGRES_URLuntuk terhubung ke database luar.
4. Definisikan Schema Database
Buat file schema di server/db/schema.ts menggunakan Drizzle ORM:
import { pgTable, text, serial, timestamp } from 'drizzle-orm/pg-core'
export const users = pgTable('users', {
id: serial().primaryKey(),
name: text().notNull(),
email: text().notNull().unique(),
phone: text(),
avatar: text().notNull(),
createdAt: timestamp().notNull().defaultNow(),
})5. Generate Migration Files
npx nuxt db generatePerintah ini akan membaca file schema.ts lalu membuat file migrasi .sql baru di folder server/db/migrations/postgresql/.
Catatan: Perintah
generatehanya membuat file SQL, belum mengubah struktur tabel apa pun di database.
6. Jalankan Migrasi ke Database
npx nuxt db migratePerintah inilah yang mengeksekusi script SQL ke database asli sehingga struktur tabel benar-benar terbarui.
npx nuxt db generate→ hanya membuat file SQL dari schema. Belum ngubah isi database.
npx nuxt db migrate→ Eksekusi file SQL untuk mengubah isi database secara manual.
npm run dev→ Saat local development, NuxtHub secara otomatis bakal menjalankan migrasi saat server dev dinyalakan.
Custom Migration & Bug di NuxtHub 0.10.8
Secara standar, cukup menjalankan:
npx nuxt db generate --custom --name nama_migrasiPada versi 0.10.8, perintah nuxt db generate --custom mengalami kendala/bug saat dijalankan.
Solusi sementara bisa buat migrasi kustom menggunakan drizzle-kit langsung dengan memanfaatkan konfigurasi dari NuxtHub:
npx drizzle-kit generate --config=./.nuxt/hub/db/drizzle.config.ts --custom --name nama_migrasiSetelah perintah di atas menghasilkan file migrasi .sql . Buka file .sql baru yang terbentuk di folder server/db/migrations/, lalu tulis query SQL kustom dan eksekusi migrasi seperti biasa.
B. Create CRUD API
Setelah schema + migration siap, giliran API. Di Nuxt, API route di simpan di server/api/. Satu file = satu endpoint atau satu method, jika menggunakan convention (index.get.ts, index.post.ts, dst).
Get Ray Fajar’s stories in your inbox
Join Medium for free to get updates from this writer.
Di FullstackNuxtHub, CRUD users disimpan diserver/api/users/:
GET /api/users→ list semua user (index.get.ts)POST /api/users→ create (index.post.ts)GET /api/users/:id→ detail ([id].get.ts)PUT /api/users/:id→ update ([id].put.ts)DELETE /api/users/:id→ delete ([id].delete.ts)
Semua query menggunakandb + schema dari @nuxthub/db (Drizzle). Filter by id menggunakaneq dari drizzle-orm dan setiap endpoint selalu mengirimkan message error.
1. List users (GET)
File: server/api/users/index.get.ts
import { db, schema } from '@nuxthub/db'
import { eq } from 'drizzle-orm'
export default eventHandler(async (event) => {
const id = Number(getRouterParam(event, 'id'))
if (!Number.isFinite(id) || id <= 0) {
throw createError({ statusCode: 400, statusMessage: 'invalid id' })
}
const [user] = await db.select().from(schema.users).where(eq(schema.users.id, id)).limit(1)
if (!user) {
throw createError({ statusCode: 404, statusMessage: 'user not found' })
}
return user
})export default eventHandler(async () => {
return await db.select().from(schema.users)
})2. Create user (POST)
Di index.post.ts: baca body (name, email, phone, avatar), validasi, insert, return row yang baru dibuat.
import { db, schema } from '@nuxthub/db'
const EMAIL_RE = /^[^\s@]+@[^\s@]+\.[^\s@]+$/
const DEFAULT_AVATAR = 'https://api.dicebear.com/9.x/initials/svg?seed=User'
function isUniqueViolation(err: unknown): boolean {
const seen = new Set<unknown>()
let cur: unknown = err
while (cur && typeof cur === 'object' && !seen.has(cur)) {
seen.add(cur)
const e = cur as { code?: string; message?: string; cause?: unknown; constraint_name?: string; constraint?: string }
if (e.code === '23505') return true
const msg = `${e.message || ''} ${e.constraint_name || ''} ${e.constraint || ''}`.toLowerCase()
if (msg.includes('unique') || msg.includes('duplicate') || msg.includes('users_email_unique')) return true
cur = e.cause
}
return false
}
export default eventHandler(async (event) => {
const body = await readBody<{
name?: string
email?: string
phone?: string | null
avatar?: string
}>(event)
const name = body?.name?.trim()
const email = body?.email?.trim()
const phone = body?.phone?.trim() || null
const avatar = body?.avatar?.trim() || DEFAULT_AVATAR
if (!name) {
throw createError({ statusCode: 400, statusMessage: 'name is required' })
}
if (!email) {
throw createError({ statusCode: 400, statusMessage: 'email is required' })
}
if (!EMAIL_RE.test(email)) {
throw createError({ statusCode: 400, statusMessage: 'email is invalid' })
}
try {
const [user] = await db
.insert(schema.users)
.values({ name, email, phone, avatar })
.returning()
return user
}
catch (err: unknown) {
if (isUniqueViolation(err)) {
throw createError({ statusCode: 409, statusMessage: 'email already exists' })
}
throw err
}
})Validasi :
namedanemailwajib.- Format email dicek regex.
phoneboleh kosong → disimpannull.avatarkosong → default (https://api.dicebear.com/9.x/initials/svg?seed=User)
3. Detail by Id (GET)
File: server/api/users/[id].get.ts
import { db, schema } from '@nuxthub/db'
import { eq } from 'drizzle-orm'
export default eventHandler(async (event) => {
const id = Number(getRouterParam(event, 'id'))
if (!Number.isFinite(id) || id <= 0) {
throw createError({ statusCode: 400, statusMessage: 'invalid id' })
}
const [user] = await db.select().from(schema.users).where(eq(schema.users.id, id)).limit(1)
if (!user) {
throw createError({ statusCode: 404, statusMessage: 'user not found' })
}
return user
})4. Delete by Id (GET)
File: server/api/users/[id].delete.ts
import { db, schema } from '@nuxthub/db'
import { eq } from 'drizzle-orm'
export default eventHandler(async (event) => {
const id = Number(getRouterParam(event, 'id'))
if (!Number.isFinite(id) || id <= 0) {
throw createError({ statusCode: 400, statusMessage: 'invalid id' })
}
const [deleted] = await db
.delete(schema.users)
.where(eq(schema.users.id, id))
.returning({ id: schema.users.id })
if (!deleted) {
throw createError({ statusCode: 404, statusMessage: 'user not found' })
}
return { ok: true, id: deleted.id }
})5. Update by Id (PUT)
File: server/api/users/[id].put.ts
import { db, schema } from '@nuxthub/db'
import { eq } from 'drizzle-orm'
const EMAIL_RE = /^[^\s@]+@[^\s@]+\.[^\s@]+$/
function isUniqueViolation(err: unknown): boolean {
const seen = new Set<unknown>()
let cur: unknown = err
while (cur && typeof cur === 'object' && !seen.has(cur)) {
seen.add(cur)
const e = cur as { code?: string; message?: string; cause?: unknown; constraint_name?: string; constraint?: string }
if (e.code === '23505') return true
const msg = `${e.message || ''} ${e.constraint_name || ''} ${e.constraint || ''}`.toLowerCase()
if (msg.includes('unique') || msg.includes('duplicate') || msg.includes('users_email_unique')) return true
cur = e.cause
}
return false
}
export default eventHandler(async (event) => {
const id = Number(getRouterParam(event, 'id'))
if (!Number.isFinite(id) || id <= 0) {
throw createError({ statusCode: 400, statusMessage: 'invalid id' })
}
const body = await readBody<{
name?: string
email?: string
phone?: string | null
avatar?: string
}>(event)
const [existing] = await db.select().from(schema.users).where(eq(schema.users.id, id)).limit(1)
if (!existing) {
throw createError({ statusCode: 404, statusMessage: 'user not found' })
}
const updates: {
name?: string
email?: string
phone?: string | null
avatar?: string
} = {}
if (body?.name !== undefined) {
const name = body.name.trim()
if (!name) {
throw createError({ statusCode: 400, statusMessage: 'name cannot be empty' })
}
updates.name = name
}
if (body?.email !== undefined) {
const email = body.email.trim()
if (!email) {
throw createError({ statusCode: 400, statusMessage: 'email cannot be empty' })
}
if (!EMAIL_RE.test(email)) {
throw createError({ statusCode: 400, statusMessage: 'email is invalid' })
}
updates.email = email
}
if (body?.avatar !== undefined) {
const avatar = body.avatar.trim()
if (!avatar) {
throw createError({ statusCode: 400, statusMessage: 'avatar cannot be empty' })
}
updates.avatar = avatar
}
if (body?.phone !== undefined) {
const phone = typeof body.phone === 'string' ? body.phone.trim() : body.phone
updates.phone = phone || null
}
if (Object.keys(updates).length === 0) {
throw createError({ statusCode: 400, statusMessage: 'no fields to update' })
}
try {
const [user] = await db
.update(schema.users)
.set(updates)
.where(eq(schema.users.id, id))
.returning()
return user
}
catch (err: unknown) {
if (isUniqueViolation(err)) {
throw createError({ statusCode: 409, statusMessage: 'email already exists' })
}
throw err
}
})C. Integrasi Frontend dengan API
Backend sudah ready, endpoint CRUD sudah lengkap. Sekarang tinggal bikin halaman Vue buat konsumsi API-nya.
File: app/pages/index.vue
1. Fetch data awal dengan useFetch
type User = {
id: number
name: string
email: string
phone: string | null
avatar: string
createdAt: string
}const { data: users, refresh, error: listError, pending } = await useFetch<User[]>('/api/users')useFetch dipanggil saat komponen pertama kali di-render, langsung hit GET /api/users yang sudah dibuat pada bagian B. Ada 4 hal yang kita ambil dari sini:
users→ data list-nyapending→ status loadinglistError→ kalau request gagalrefresh→ buat re-fetch manual, dipanggil lagi tiap habis create/update/delete biar list-nya update
2. State untuk form create & edit
const form = reactive({
name: '',
email: '',
phone: '',
avatar: '',
})
const editingId = ref<number | null>(null)
const editForm = reactive({
name: '',
email: '',
phone: '',
avatar: '',
})3. Create user dengan $fetch
async function createUser() {
formError.value = ''
actionPending.value = true
try {
await $fetch('/api/users', {
method: 'POST',
body: {
name: form.name,
email: form.email,
phone: form.phone || undefined,
avatar: form.avatar || undefined,
},
})
form.name = ''
form.email = ''
form.phone = ''
form.avatar = ''
await refresh()
}
catch (err: unknown) {
formError.value = extractError(err)
}
finally {
actionPending.value = false
}
}- Reset error dulu
- POST ke
/api/users - sukses → reset form +
refresh()list ke-update - gagal → tangkap error-nya lewat
extractError()
4. Edit user
function startEdit(user: User) {
editingId.value = user.id
editForm.name = user.name
editForm.email = user.email
editForm.phone = user.phone || ''
editForm.avatar = user.avatar
editError.value = ''
}function cancelEdit() {
editingId.value = null
editError.value = ''
}
async function saveEdit() {
if (editingId.value == null) return
editError.value = ''
actionPending.value = true
try {
await $fetch(`/api/users/${editingId.value}`, {
method: 'PUT',
body: {
name: editForm.name,
email: editForm.email,
phone: editForm.phone,
avatar: editForm.avatar,
},
})
editingId.value = null
await refresh()
}
catch (err: unknown) {
editError.value = extractError(err)
}
finally {
actionPending.value = false
}
}5. Delete user
async function removeUser(id: number) {
if (!confirm(`Delete user #${id}?`)) return
formError.value = ''
actionPending.value = true
try {
await $fetch(`/api/users/${id}`, { method: 'DELETE' })
if (editingId.value === id) cancelEdit()
await refresh()
}
catch (err: unknown) {
formError.value = extractError(err)
}
finally {
actionPending.value = false
}
}6. Helper extract error message
function extractError(err: unknown): string {
const e = err as { data?: { statusMessage?: string; message?: string }; statusMessage?: string; message?: string }
return e?.data?.statusMessage || e?.data?.message || e?.statusMessage || e?.message || 'Request failed'
}7. Template Frontend
<template>
<main class="wrap">
<section class="card">
<h2>Create user</h2>
<form class="form" @submit.prevent="createUser">
<label>Name <input v-model="form.name" /></label>
<label>Email <input v-model="form.email" type="email" /></label>
<label>Phone <input v-model="form.phone" type="tel" placeholder="optional" /></label>
<label>Avatar URL <input v-model="form.avatar" placeholder="optional" /></label>
<button type="submit" :disabled="actionPending">Create</button>
</form>
<p v-if="formError" class="error">{{ formError }}</p>
</section>
<section class="card">
<h2>Users</h2>
<p v-if="pending">Loading…</p>
<p v-else-if="listError" class="error">{{ listError.message || 'Failed to load users' }}</p>
<p v-else-if="!users?.length">No users yet.</p>
<ul v-else class="list">
<li v-for="user in users" :key="user.id" class="item">
<div v-if="editingId !== user.id" class="row">
<img :src="user.avatar" alt="" class="avatar" width="40" height="40" />
<div class="meta">
<strong>#{{ user.id }} {{ user.name }}</strong>
<span>{{ user.email }}</span>
<span v-if="user.phone">{{ user.phone }}</span>
<small>{{ user.createdAt }}</small>
</div>
<div class="actions">
<button type="button" @click="startEdit(user)">Edit</button>
<button type="button" class="danger" :disabled="actionPending" @click="removeUser(user.id)">Delete</button>
</div>
</div>
<form v-else class="form edit" @submit.prevent="saveEdit">
<label>Name <input v-model="editForm.name" /></label>
<label>Email <input v-model="editForm.email" type="email" /></label>
<label>Phone <input v-model="editForm.phone" type="tel" placeholder="optional" /></label>
<label>Avatar URL <input v-model="editForm.avatar" /></label>
<div class="actions">
<button type="submit" :disabled="actionPending">Save</button>
<button type="button" @click="cancelEdit">Cancel</button>
</div>
<p v-if="editError" class="error">{{ editError }}</p>
</form>
</li>
</ul>
</section>
</main>
</template>
<style scoped>
.wrap { max-width: 720px; margin: 2rem auto; padding: 0 1rem; font-family: system-ui, sans-serif; }
.card { border: 1px solid #ddd; border-radius: 8px; padding: 1rem; margin-bottom: 1.5rem; }
.form { display: grid; gap: 0.5rem; }
.form label { display: grid; gap: 0.25rem; font-size: 0.9rem; }
input { padding: 0.4rem 0.5rem; border: 1px solid #ccc; border-radius: 4px; }
button { padding: 0.4rem 0.75rem; cursor: pointer; }
.danger { color: #b00020; }
.error { color: #b00020; margin: 0.5rem 0 0; }
.list { list-style: none; padding: 0; margin: 0; display: grid; gap: 0.75rem; }
.item { border-top: 1px solid #eee; padding-top: 0.75rem; }
.item:first-child { border-top: 0; padding-top: 0; }
.row { display: flex; gap: 0.75rem; align-items: center; }
.avatar { border-radius: 50%; object-fit: cover; background: #f0f0f0; }
.meta { display: grid; flex: 1; gap: 0.15rem; }
.meta small { color: #666; }
.actions { display: flex; gap: 0.4rem; }
.edit { margin-top: 0.25rem; }
</style>D. Catatan
Ada dua halmenarik dari NuxtHub ini, walau gak masuk ke alur utama CRUD di atas.
- Soal CORS — gak perlu setup
Biasanya kalau FE dan BE terpisah (misal FE Vue/React di port 5173, BE Express/Golang di port 3000), kita wajib setting CORS di backend biar browser gak nge-block request cross-origin. Nah di NuxtHub, ini otomatis gak jadi masalah, karena FE (app/pages/) dan BE (server/api/) sama-sama di-build dan di-serve dari satu Nitro server yang sama. Request kayak $fetch('/api/users') itu dipanggil pakai path relatif, bukan full URL ke domain lain, jadi browser nganggepnya same-origin — gak ada preflight OPTIONS, gak ada header Access-Control-Allow-Origin yang perlu diatur manual.
2. Bisa cek database langsung lewat Nuxt DevTools.
Gak perlu buka pgAdmin, DBeaver, atau query manual di terminal buat ngecek isi database. Tinggal jalankan npm run dev, buka Nuxt DevTools (icon Nuxt di pojok bawah browser, atau Shift + Option/Alt + D), lalu masuk ke tab Hub → sub-menu Database. Di situ semua tabel dari schema (server/db/schema.ts) ke-list, isi data per-row bisa di-browse real-time, jadi abis POST/PUT/DELETE lewat FE tinggal refresh panel ini buat verifikasi data beneran ke-update — gak perlu bolak-balik ke tool DB terpisah. Bisa run query SQL manual juga kalau butuh cek sesuatu yang lebih spesifik.








