Validation

This lesson covers Validation. Here is the idea in simple words, then we write real code.

What you will learn

• What validation means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: CRUD Operations — Complete Guide

Explain it simply

Validation checks user input before it hits your database — required fields, email format, number ranges.

Why developers use this

• Powers mobile and web clients
• Good APIs prevent bugs
• Employers expect this

How it works (step by step)

1. Client sends HTTP method + URL + optional JSON body.
2. Server validates input — reject bad data with 400.
3. Business logic reads or writes the database.
4. Response is JSON with a clear message the frontend can show.

Code example — type this yourself

const { z } = require('zod');
const schema = z.object({ email: z.string().email(), age: z.number().min(18) });
const data = schema.parse(req.body);

Use Zod or Joi. Return 400 with clear error messages when validation fails.

What each part does

• const { z } = require('zod'); — Loads a built-in module or package you installed with npm.
• const schema = z.object({ email: z.string().email(), age: z.number().min(18) }); — Line 2: runs as written.
• const data = schema.parse(req.body); — Line 3: runs as written.

Real life: where Validation shows up

A mobile app talks to a Node backend using Validation. The phone sends JSON; the server validates, saves to PostgreSQL, and returns clear success or error messages.

Try it yourself — hands-on

1. Create a new file (e.g. validation-demo.js) in an empty folder
2. Type the example code for Validation yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — Validation only feels easy after you run code yourself.

Interview note

Be ready to explain Validation with a real trade-off: what problem it solves and what you would not use it for.

Summary

• You can explain Validation in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this