AI Workshop: learn to build apps with AI →
Configuration: Next.js, adding features just to development mode

Join the AI Workshop and learn to build real-world apps with AI. A hands-on, practical program to level up your skills.


Some sites/apps I work on have 2 modes. One is the development mode, the other is production, the live version.

With Next.js I find this very easy to do by checking the value of process.env.NODE_ENV, which is set to 'development' when running it with npm run dev.

So I might have an API route that should not be public, and at the top of it, I add

if (process.env.NODE_ENV != 'development') return null

so it does not work in production.

The same applies to a page component, which will render a blank page if accessed in production.

I use the same technique to add JSX to a component only in development mode:

{
  process.env.NODE_ENV == 'development' && <div>hi</div>
}

Lessons in this unit:

0: Introduction
1: Absolute imports in Next.js
2: How to change a Next.js app port
3: ▶︎ Next.js, adding features just to development mode
4: Next.js: how to show something in development and hide in production
5: Adding a wrapper component to your Next.js app