Deploying a Next.js app in production
How to generate the production version of your Next.js app
Deploying an app made using Next.js in production is easy. Add those 3 lines to the package.json
script
section:
"scripts": {
"dev": "next",
"build": "next build",
"start": "next start"
}
We used npm run dev
up to now, to call the next
command installed locally in node_modules/next/dist/bin/next
. This started the development server, which provided us source maps and hot code reloading, two very useful features while debugging.
The same command can be invoked to build the website passing the build
flag, by running npm run build
. Then, the same command can be used to start the production app passing the start
flag, by running npm run start
.
Those 2 commands are the ones we must invoke to successfully deploy the production version of our site locally. The production version is highly optimized and does not come with source maps and other things like hot code reloading that would not be beneficial to our end users.
So, let’s create a production deploy of our app. Build it using:
npm run build
The output of the command tells us that some routes (/
and /blog
are now prerendered as static HTML, while /blog/[id]
will be served by the Node.js backend.
Then you can run npm run start
to start the production server locally:
npm run start
Visiting http://localhost:3000 will show us the production version of the app, locally.
→ I wrote 17 books to help you become a better developer:
- C Handbook
- Command Line Handbook
- CSS Handbook
- Express Handbook
- Git Cheat Sheet
- Go Handbook
- HTML Handbook
- JS Handbook
- Laravel Handbook
- Next.js Handbook
- Node.js Handbook
- PHP Handbook
- Python Handbook
- React Handbook
- SQL Handbook
- Svelte Handbook
- Swift Handbook
Also, JOIN MY CODING BOOTCAMP, an amazing cohort course that will be a huge step up in your coding career - covering React, Next.js - next edition February 2025