Joi as validation alternative in Express

Introduction

Joi helps you check if data is correct before using it. It makes sure your app gets good data and avoids errors.

When you want to check user input in forms before saving it.

When you receive data from an API and want to make sure it looks right.

When you want to avoid crashes caused by wrong or missing data.

When you want to give clear messages to users about what data is wrong.

When you want to keep your code clean by separating data checks from main logic.

Syntax

Express

const Joi = require('joi');

const schema = Joi.object({
  name: Joi.string().min(3).max(30).required(),
  age: Joi.number().integer().min(0).max(120),
  email: Joi.string().email().required()
});

const { error, value } = schema.validate(data);

Use Joi.object() to define the shape of your data.

Call schema.validate(data) to check data and get errors if any.

Examples

This checks if a string is at least 5 characters long and is present.

Express

const schema = Joi.string().min(5).required();
const { error } = schema.validate('hello');

This checks if a number is an integer between 1 and 10.

Express

const schema = Joi.number().integer().min(1).max(10);
const { error } = schema.validate(7);

This checks an object with username and password rules.

Express

const schema = Joi.object({
  username: Joi.string().alphanum().min(3).max(15).required(),
  password: Joi.string().pattern(new RegExp('^[a-zA-Z0-9]{3,30}$'))
});
const { error } = schema.validate({ username: 'user1', password: 'abc123' });

Sample Program

This Express app uses Joi to check user data sent to /user. If data is wrong, it sends an error message. If data is good, it confirms success.

Express

const express = require('express');
const Joi = require('joi');

const app = express();
app.use(express.json());

const userSchema = Joi.object({
  name: Joi.string().min(3).max(30).required(),
  email: Joi.string().email().required(),
  age: Joi.number().integer().min(0).max(120)
});

app.post('/user', (req, res) => {
  const { error, value } = userSchema.validate(req.body);
  if (error) {
    return res.status(400).send({ message: error.details[0].message });
  }
  res.send({ message: 'User data is valid', data: value });
});

app.listen(3000, () => console.log('Server running on port 3000'));

Important Notes

Joi gives detailed error messages to help fix data problems.

Always validate data before using it to keep your app safe.

You can customize Joi rules to fit your exact needs.

Summary

Joi helps check data easily and clearly.

Use Joi to avoid bugs from bad data.

It works well with Express to keep your app safe and clean.

Practice

1. What is the main purpose of using Joi in an Express application?

easy

A. To serve static files like images and CSS

B. To handle routing between different pages

C. To connect to a database

D. To validate incoming data and ensure it meets expected rules

Solution

1. Step 1: Understand Joi's role

   Joi is a library designed to check if data matches certain rules before using it.

2. Step 2: Compare with other Express tasks

   Routing, database connection, and serving files are handled by other parts of Express or middleware, not Joi.

3. Final Answer:

   To validate incoming data and ensure it meets expected rules -> Option D

4. Quick Check:

   Joi validates data = A [OK]

Hint: Joi is all about checking data rules fast [OK]

Common Mistakes:

• Confusing Joi with routing or database tools
• Thinking Joi serves files
• Assuming Joi manages app navigation

2. Which of the following is the correct way to define a Joi schema for a required string named username?

easy

A. const schema = Joi.string().required();

B. const schema = Joi.required().string();

C. const schema = Joi.string.required();

D. const schema = Joi.string().isRequired();

Solution

1. Step 1: Recall Joi syntax for strings

   Joi.string() creates a string schema, and .required() marks it as mandatory.

2. Step 2: Check method chaining order

   The correct chaining is Joi.string().required(), not Joi.required().string() or others.

3. Final Answer:

   const schema = Joi.string().required(); -> Option A

4. Quick Check:

   Joi.string().required() syntax = B [OK]

Hint: Use Joi.string().required() to make a string mandatory [OK]

Common Mistakes:

• Placing .required() before .string()
• Using .isRequired() which is not a Joi method
• Missing parentheses after string()

3. Given this Joi schema and data:

const schema = Joi.object({ age: Joi.number().min(18).required() });
const data = { age: 16 };
const result = schema.validate(data);

What will result.error contain?

medium

A. Null because Joi does not check numbers

B. Null because age is valid

C. An error object because age is less than 18

D. An error object because age is missing

Solution

1. Step 1: Understand the schema rules

   The schema requires age to be a number, at least 18, and present.

2. Step 2: Check the data against rules

   Data has age = 16, which is less than the minimum 18, so validation fails.

3. Final Answer:

   An error object because age is less than 18 -> Option C

4. Quick Check:

   Age 16 < 18 causes error = D [OK]

Hint: Min 18 means below 18 triggers error [OK]

Common Mistakes:

• Thinking 16 passes min(18)
• Assuming missing age error instead
• Believing Joi ignores number checks

4. You wrote this code to validate an email:

const schema = Joi.object({ email: Joi.string().email() });
const data = { email: 12345 };
const result = schema.validate(data);

What is the main problem here?

medium

A. The email method is missing parentheses

B. The email field is not a string, so validation fails

C. Joi.string() cannot be used with email validation

D. The schema object is missing .required()

Solution

1. Step 1: Check data type for email

   Email expects a string, but data has a number (12345), which is invalid.

2. Step 2: Confirm Joi email method usage

   Joi.string().email() is correct syntax; parentheses are present.

3. Final Answer:

   The email field is not a string, so validation fails -> Option B

4. Quick Check:

   Email must be string, got number = A [OK]

Hint: Email must be string, numbers cause validation error [OK]

Common Mistakes:

• Ignoring data type mismatch
• Thinking .email() needs no parentheses
• Assuming .required() is always needed

5. You want to validate a user object with name (string, required), age (optional number, min 0), and email (required valid email). Which Joi schema correctly enforces these rules?

hard

A. Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() })

B. Joi.object({ name: Joi.string(), age: Joi.number().min(0).required(), email: Joi.string().email() })

C. Joi.object({ name: Joi.string().required(), age: Joi.number().min(0).required(), email: Joi.string().email() })

D. Joi.object({ name: Joi.string(), age: Joi.number(), email: Joi.string().email().required() })

Solution

1. Step 1: Check required fields

   Name and email must be required, so .required() must be on both.

2. Step 2: Check optional age with min 0

   Age is optional, so no .required(), but min(0) applies.

3. Step 3: Validate each option

   Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() }) matches all rules exactly; others miss required or optional correctly.

4. Final Answer:

   Joi.object({ name: Joi.string().required(), age: Joi.number().min(0), email: Joi.string().email().required() }) -> Option A

5. Quick Check:

   Required name/email, optional age min 0 = C [OK]

Hint: Required fields get .required(), optional just rules [OK]

Common Mistakes:

• Marking optional age as required
• Missing .required() on name or email
• Confusing order of chaining methods