Forem: AD

Next.js 15.5 is here with game-changing updates!

AD — Mon, 25 Aug 2025 12:46:31 +0000

Here's what devs need to know:

Turbopack in Beta: Production builds via next build --turbopack – already handling 1.2B+ requests on http://nextjs.org. Projects seeing 2-5x faster builds, slashing deployment times!
Stable Node.js Middleware: No more Edge limits – full access to fs, crypto, and npm packages. Perfect for complex logic like secure token gen. Set runtime: 'nodejs' and level up your server-side game.
Linting Shift: next lint deprecated (gone in v16). Time to switch to ESLint or Biome manually. Start migrating now to avoid headaches.
TypeScript Boosts: Typed routes, route export validation, and global PageProps/LayoutProps. Enable typedRoutes: true for compile-time checks, plus new next typegen for CI validation.

Deprecations Ahead: Warnings for legacyBehavior, AMP, Image quality configs, and more – clean up before Next.js 16 drops.

These updates make Next.js even more powerful for real-world apps. For the full breakdown and migration tips, head over to :

To dive deeper!

Next.js 15.5

I decided to go back to using VS Code.

AD — Mon, 11 Aug 2025 09:03:09 +0000

Right now, I'm going back to using good old VS Code because I want to test out the GitHub Copilot it offers. They've added updates to the tool, but the UI is still the same. However, they now offer all the AI options.
Especially GPT5, which is getting a lot of buzz right now.

Basically, the purpose of using an IDE is to code. It's true that there are differences between IDEs. Switching from one to another would take time to adapt. Even though I think Cursor is the most powerful in this field.

But here's what I suggest. VS Code with Claude Code. In my opinion, this is the best way to code, as the two complement each other effectively. One can think about one thing while the other can work with several agents at the same time.

In terms of price, Copilote offers a free one-month trial if you subscribe. Claude Code starts at $17. The choice is yours.

What are you currently using to code?

How to Upgrade to Prisma 6 (Without Breaking Everything)

AD — Tue, 05 Aug 2025 13:18:35 +0000

Thinking of upgrading to Prisma v6?
Don't do it blind.

Prisma 6 brings some major changes — especially in how the Client is generated and used.

And if you're using custom output paths or working in a monorepo, there are a few gotchas you’ll want to avoid.

I just published a step-by-step guide that covers:

✅ What changed in Prisma 6 (output paths, setup, CLI)
🛠️ How to migrate safely with examples
🧼 How to clean up your old setup to avoid conflicts
🧪 Bonus: testing your new setup with minimal downtime

👉 If you're using Prisma in a modern TypeScript or fullstack project (especially Next.js), this will save you hours.

Prisma V6

Better Auth + Prisma: Secure Auth in Next.js App Router

AD — Wed, 16 Jul 2025 13:25:50 +0000

Most devs still fumble auth when using the App Router in Next.js.

And I get it — juggling:
API routes
secure token handling
and clean form validation with shadcn...

It’s easy to fall back on boilerplate or legacy auth flows that barely work.

That’s exactly the problem I hit when I tried integrating Better Auth with Prisma — using only the Next.js App Router (no pages directory, no hacks).

Here’s what I tackled:

🔐 Clean sign-

up/login with email + password
✅ Form validation with shadcn/ui forms + Zod
📦 Full DB integration using Prisma
🧠 Session + token handling with middleware, not just cookie tricks
🧪 Safe actions via next-safe-action

All in one consistent auth system — no magic, no vendor lock-in.

If you're building a modern full-stack app with Next.js 15+ and want an auth system that’s secure, simple, and future-proof, I wrote up the guide here:

👇
App Router + Server Actions + Prisma

What would you add or do differently? Curious to see how others are handling auth.

Grok 4 Is Here — And It’s Equal Parts Genius and Nightmare

AD — Fri, 11 Jul 2025 07:33:06 +0000

Elon Musk just dropped a $300/month AI—and it's not ChatGPT.
It’s called 👉Grok 4.
▶️ It claims to beat PhDs in every subject.
▶️ It can reason better than most humans.
▶️ And it just launched with super-agent mode.

But here's the part that got me:

Grok 4 isn’t just another language model.
According to Musk, it’s post-grad level in every subject.
And the premium tier—SuperGrok Heavy—spawns multiple AIs to work on a single problem like a study group. Then they vote on the best answer.

It even beat OpenAI’s latest on the “Humanity’s Last Exam.”
No tools. Just raw reasoning.
📊 25.4% score without tools.
📊 44.4% score with tools (beating Gemini and GPT-4o variants).

But here’s where it gets complicated.
Last week, Grok’s official account on X (formerly Twitter) made antisemitic comments.

It sparked major backlash—and Musk’s team tried to quietly tweak Grok’s system prompt.

That’s the tension right now:
▶️A model that pushes benchmarks forward
▶️A team that’s still playing cleanup on misalignment

As someone building in AI, this launch gave me whiplash.
▶️On one hand, the tech is wild.
▶️On the other, it reminds me how brittle alignment still is.

Would you pay $300/month for this?
Is xAI bold—or just reckless?
👇 Drop your take in the comments.
🔗 Full breakdown + newsletter here: https://www.npmix.com/blog/grok-4-is-here-and-its-equal-parts-genius-and-nightmare

I Built a CLI That Saves Developers 6 Hours on Every New TypeScript Project

AD — Wed, 25 Jun 2025 12:01:21 +0000

Last month, I tracked how much time I spent on project setup.

The result? 27 hours across 4 new projects.

That's almost a full work week just configuring tools instead of building features.

So I used Better-T-Stack CLI to solve this problem once and for all.

The Problem Every TypeScript Developer Faces

Starting a new project means making dozens of decisions:

Which frontend framework?
How to structure the backend?
Which database and ORM?
What auth solution?
How to ensure type safety across the stack?
Which deployment platform?

Then you spend hours:

Reading documentation
Configuring each tool
Making them work together
Debugging when they don't
Setting up best practices

By the time you're done, you've lost momentum and haven't written a single feature.

The Solution: One Command Setup

Better-T-Stack CLI eliminates all this friction:

npx create-better-t-stack@latest

An interactive wizard walks you through choosing your stack, then generates a production-ready project with everything configured correctly.

What Makes It Different

Full Type Safety Every combination ensures types flow from your database schema to your UI components. No any types, no runtime surprises.
Proven Combinations
Instead of guessing which packages work well together, you get battle-tested stacks that thousands of developers use in production.
Best Practices Built-In

Proper folder structure
ESLint and Prettier configured
Git hooks with Husky
TypeScript paths set up correctly
Environment variable handling
Error boundaries and logging

46+ Package Options Mix and match from:

Frontend: Next.js, Astro, SvelteKit, Remix, Nuxt
Backend: Next.js, Express, Fastify, Hono
Database: PostgreSQL, MySQL, SQLite
ORM: Drizzle, Prisma
Auth: Better-auth

Try It Yourself

Run npx create-better-t-stack@latest
Choose your preferred technologies
Start coding instantly

Check it out: better-t-stack.dev
The repository is open source: GitHub

What's Next?

I'm working on adding more frameworks and deployment options based on community feedback.
What stack combination would you want to see added? Let me know in the comments.

Building tools that save developers time is my passion. Follow me for more developer productivity tips and open source projects.

Stop Building Bad Search Bars — A Smarter Search Hook with React & Next.js App Router

AD — Tue, 24 Jun 2025 12:04:53 +0000

Most apps have terrible search UX.
It’s slow, filters too soon, lacks debounce, and frustrates users.
I built a simple but powerful reusable useSearch hook for React using Next.js App Router.

With just 2 hooks, you create a fast, smooth, reusable search system that can power many parts of your app.

✅ Better UX
✅ Easy to maintain
✅ Simple to extend

👉 Full tutorial with full context here: https://www.npmix.com/blog/react-usesearch-hook-build-a-smarter-search-system-in-your-app

Migrating from Auth.js to Better Auth — Full Guide for Next.js App Router

AD — Fri, 20 Jun 2025 09:30:52 +0000

Most Next.js 15 projects still rely on Auth.js — but Better Auth offers a much smoother experience, fully compatible with the App Router and React 19.

In this guide, I show you how to:

✅ Install Better Auth
✅ Set up your config
✅ Use new client-side hooks
✅ Handle sessions securely on server actions

Full guide here 👉 Migrating from Auth.js to Better Auth in Next.js 15

If you're planning an authentication upgrade soon, this might save you hours.

Let's discuss in comments if you have questions or run into issues!

Building a Smart BlurImage Component in Next.js 15 App Router

AD — Thu, 19 Jun 2025 09:44:59 +0000

Elevate your Next.js 15 app with a smart BlurImage component! Smooth blur effects while images load—no janky placeholders.

1️⃣Why it’s a must-have:
-Seamless UX with blur placeholders
-Built on Next.js 15’s
-Lightweight: just React + CSS -Perfect for App Router apps!

2️⃣How it works:
-useState tracks load state
-CSS blur(5px) until loaded
-Pair with blurDataURL for AI images (Flux, anyone?)

3️⃣Make it yours:
-Tweak blur intensity
-Add transitions for polish
-Test with Flux or OpenAI-generated images

4️⃣Ship better Next.js apps today! Try BlurImage & share your results—how’s it look with your stack? 👇

BlurImage Component in Next.js

React 19's use Hook: 2 Weeks in Production (The Good, Bad, and Ugly)

AD — Tue, 17 Jun 2025 13:02:41 +0000

Two weeks ago, I decided to migrate our Next.js 15 app to use React 19's new use hook for all data fetching.

Here's what actually happened (spoiler: it wasn't all smooth sailing).

What We'll Cover

Why we migrated (and why you might want to wait)
Real performance numbers from production
3 gotchas that will bite you
Code examples from our actual codebase
When to use use vs sticking with useEffect

The Setup

Our app: E-commerce dashboard with real-time analytics
Tech stack: Next.js 15, React 19, TypeScript
Team size: 5 developers (2 junior, 3 senior)
Traffic: ~50k daily users

The Migration Decision

We weren't chasing the latest shiny thing. Our data fetching code had real problems:

17 different loading state patterns across components
Inconsistent error handling
Race conditions in useEffect chains
Junior devs struggling with async state management The use hook promised to solve all of this. But did it?

Continue reading for the full implementation guide...

Build an AI-powered image generator with Next.js & Flux.1 Kontext!

AD — Tue, 17 Jun 2025 12:58:03 +0000

Create or edit stunning visuals in seconds using text prompts. Follow this step-by-step tutorial to integrate Flux.1's cutting-edge API.

Here the link for more : 👇
Build AI Image Generator in Next.js with Flux.1 Kontext

Build an AI-powered image generator with Next.js & Flux.1 Kontext!

AD — Thu, 05 Jun 2025 07:44:15 +0000

Create or edit stunning visuals in seconds using text prompts. Follow this step-by-step tutorial to integrate Flux.1's cutting-edge API.

Here the link for more : 👇
Build AI Image Generator in Next.js with Flux.1 Kontext