Next.js, adding features just to development mode
New Course Coming Soon:
Get Really Good at Git
How to make features available in development mode, while hiding them in production
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 so 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>
}
Are you intimidated by Git? Can’t figure out merge vs
rebase? Are you afraid of screwing up something any time
you have to do something in Git? Do you rely on ChatGPT
or random people’s answer on StackOverflow to fix your
problems? Your coworkers are tired of explaining Git to
you all the time? Git is something we all need to use,
but few of us really master it. I created this course to
improve your Git (and GitHub) knowledge at a radical
level. A course that helps you feel less frustrated with
Git. Launching Summer 2024. Join the waiting list!
→ Get my
Next.js (pages router) Handbook
Here is how can I help you:
- COURSES where I teach everything I know
- THE VALLEY OF CODE your web development manual
- BOOTCAMP 2024 cohort in progress, next edition in 2025
- BOOKS 16 coding ebooks you can download for free on JS Python C PHP and lots more
- SOLO LAB everything I know about running a lifestyle business as a solopreneur
- Interesting links collection
- Follow me on X