So far we've developed and run sample NEXT.JS application in dev mode, now we'll do the production ready deployment locally using following steps.
npm run build − Build the production ready, highly optimized build.
npm run start − Start the server.
The production ready build lacks source maps and hot code reloading as compared to dev mode as those features are primarily used in debugging.
Run the following command to prepare production ready build −.
npm run build > email@example.com build \Node\nextjs > next build info - Loaded env from \Node\nextjs\.env.local Creating an optimized production build Compiled successfully. Automatically optimizing pages Page Size First Load JS + ? / 2.25 kB 60.3 kB + /_app 288 B 58.1 kB + /404 3.25 kB 61.3 kB + ? /api/user + ? /posts/[id] 312 B 61.6 kB + + /posts/one + + /posts/two + ? /posts/env 2.71 kB 60.8 kB + ? /posts/first 374 B 61.7 kB + First Load JS shared by all 58.1 kB + static/pages/_app.js 288 B + chunks/3458401054237127135bcd3ee8eb2a19d67af299.a1a019.js 10.5 kB + chunks/framework.c6faae.js 40 kB + runtime/main.60464f.js 6.54 kB + runtime/webpack.c21266.js 746 B + css/9706b5b8ed8e82c0fba0.css 175 B ? (Server) server-side renders at runtime (uses getInitialProps or getServerSideProps) (Static) automatically rendered as static HTML (uses no initial props) ? (SSG) automatically generated as static HTML + JSON (uses getStaticProps)
Run the following command to start production server −.
npm run start > firstname.lastname@example.org start \Node\nextjs > next start info - Loaded env from \Node\nextjs\.env.local ready - started server on http://localhost:3000
Open localhost:3000/api/user in a browser and you will see the following output.