Why production setup differs from development in Node.js

Introduction

Production setup is made to keep apps fast, safe, and stable for real users. Development setup helps programmers build and test code easily.

When you want to make sure your app runs smoothly for visitors.

When you need to find and fix bugs during coding.

When you want to test new features without affecting real users.

When you want to protect your app from hackers and errors in live use.

When you want to improve app speed and reduce resource use for many users.

Syntax

Node.js

// Example: Different environment variables for dev and prod
// .env.development
PORT=3000
DEBUG=true

// .env.production
PORT=80
DEBUG=false

Use environment variables to switch settings between development and production.

Development often includes extra tools like debuggers and live reload.

Examples

This code runs extra debug messages only in development.

Node.js

if (process.env.NODE_ENV === 'development') {
  console.log('Debug info shown');
} else {
  console.log('Running in production mode');
}

Security tools like Helmet are added only in production to protect the app.

Node.js

const express = require('express');
const app = express();

if (process.env.NODE_ENV === 'production') {
  app.use(require('helmet')()); // Security middleware
}

app.listen(process.env.PORT || 3000);

Sample Program

This simple Node.js server logs request details only in development mode. In production, it stays quiet for better performance.

Node.js

import http from 'http';

const PORT = process.env.PORT || 3000;
const NODE_ENV = process.env.NODE_ENV || 'development';

const server = http.createServer((req, res) => {
  if (NODE_ENV === 'development') {
    console.log(`Request received: ${req.method} ${req.url}`);
  }
  res.writeHead(200, {'Content-Type': 'text/plain'});
  res.end('Hello World');
});

server.listen(PORT, () => {
  console.log(`Server running in ${NODE_ENV} mode on port ${PORT}`);
});

Important Notes

Never expose sensitive info like passwords in production logs.

Use tools like PM2 or Docker to manage production apps safely.

Always test your production setup in a staging environment before going live.

Summary

Development setup helps programmers build and debug easily.

Production setup focuses on speed, security, and stability for users.

Use environment variables to switch between these setups smoothly.