Studio Ghibli Meets ShadCN, and Why ‘server-only’ Just Saved My App

Hey Reader,

🎨 Ever wanted your website to feel like it came straight out of a Studio Ghibli movie?

I just discovered a Ghibli-inspired ShadCN UI theme that brings that dreamy, hand-painted magic to your components — and it’s absolutely stunning.

If you're as obsessed with that aesthetic as I am, you're gonna love this.

I also share a Github Repo you can check out too that goes along well with the video.

🍿 Weekly Snack: 'server-only' vs 'use server'

Next.js has two easily confused directives: 'use server' and server-only.

💡 server-only has nothing to do with Server Actions.

'use server' marks a function to run on the server and be exposed as an HTTP endpoint — that’s a Server Action.

But it doesn't prevent the file from being imported in a client component — which causes runtime failures, often in production.

That’s why server-only exists: It enforces a hard boundary, throwing an error if you import server code on the client — so mistakes fail early, not late.

✅ `'use server'`

→ Specifically for Server Actions

→ This function is allowed to run on the server only, and can be called from the client via form submissions or imperative actions

→ Enforced at runtime, not build time

✅ `server-only`

→ Not related to Server Actions at all

→ Just a safety guard 🔐 that says: “This file must never be used in a client component or client context”

→ Enforced at build time, not runtime

⚠️ Key TakeAways

→ Don’t use server-only on Server Actions but for database helpers, private APIs, or files that access environment variables.
→ You can’t rely on 'use server' to protect sensitive server modules.

→ Use them side-by-side in a project, but not in the same file.

🚀 Latest Frontend News

🧰 Supabase dropped their official UI Library ↗ — built with ShadCN registry, works with React, Next.js, TanStack.
Includes login, dropzone, real-time avatars/chat, and AI prompts.

⚡ Vite published a dev server security patch. Update if you're on any of these versions: 6.2.4, 6.1.3, 6.0.13, 5.4.16, 4.5.11

⚙️ Next.js 15.2.3 includes a security fix too — update or follow the mitigation steps ↗. Hosted apps on Vercel, Netlify, and Cloudflare are safe.

🚢 Windsurf Wave 6 is live — now supports one-click deployment ↗. Fast and super dev-friendly.

Ready to multithread everything with Cursor 0.48 ↗ few cool things are,

🧩 Multi-tab chats for parallel workflows (Cmd+T).
🔎 Faster Indexing: Shared codebases now index dramatically faster (e.g., Cursor repo: 20 min → under 1 min).
🔔 Sound Notification: Audio cue when AI response is ready.
🤑 Cost Visibility: See cost per chat (usage-based plans).

⚙️ Prisma published 2 ways to integrate Trigger.dev into a Next.js + Turborepo app ↗ — with working monorepo setups.

🚀 Deploy Next.js anywhere you like, check this RFC

React 19.1 just dropped 💥 — here’s what’s worth a look:

🕵️‍♀️ Debug smarter with the new Owner Stack (dev-only), making it easier to trace who rendered what.
⏳ Suspense is now everywhere — client, server, even during hydration — with cleaner fallback behavior and better scheduling.
🧪 Experiment with unstable_prerender in React Server Components, now with edge streaming support.