User registration flow in Express - Step-by-Step Execution

Concept Flow - User registration flow

User submits registration form

↓

Server receives POST /register

↓

Validate input data

↓

Check if user exists

↓

Hash password

↓

Save user to DB

↓

Send success response

↓

User registered successfully

This flow shows how a user registration request is handled step-by-step from form submission to saving user data or sending errors.

Execution Sample

Express

app.post('/register', async (req, res) => {
  const { username, password } = req.body;
  if (!username || !password) return res.status(400).send('Missing data');
  const exists = await User.findOne({ username });
  if (exists) return res.status(409).send('User exists');
  const hash = await hashPassword(password);
  await User.create({ username, password: hash });
  res.status(201).send('Registered');
});

This code handles user registration by checking input, verifying user existence, hashing password, saving user, and sending response.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Receive POST /register	Request body: {username:'alice', password:'1234'}	Proceed to validation
2	Validate input	username and password present?	Yes, continue
3	Check if user exists	User.findOne({username:'alice'})	No user found
4	Hash password	hashPassword('1234')	Password hashed
5	Save user	User.create({username:'alice', password:hashed})	User saved in DB
6	Send response	Status 201	Response: 'Registered' sent
7	End	Process complete	User registration successful

💡 Process stops after sending success response or error if any validation fails

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
username	undefined	'alice'	'alice'	'alice'	'alice'	'alice'
password	undefined	'1234'	'1234'	'1234'	'1234'	'1234'
exists	undefined	undefined	null (no user)	null	null	null
hash	undefined	undefined	undefined	'hashedPassword'	'hashedPassword'	'hashedPassword'

Key Moments - 3 Insights

Why do we check if username and password exist before proceeding?

Because if either is missing, the server should stop and send an error (see execution_table step 2). This prevents saving incomplete data.

What happens if the username already exists in the database?

The server sends a 409 error response and stops registration (not shown in this example but would happen after step 3 if exists is true).

Why do we hash the password before saving?

To keep user passwords safe. Storing plain passwords is risky. Hashing transforms it into a secure form (see step 4).

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'exists' after step 3?

A null (no user found)

B 'alice'

C undefined

D 'hashedPassword'

💡 Hint

Check the 'exists' variable in variable_tracker after step 3

At which step does the server send the success response?

A Step 4

B Step 6

C Step 2

D Step 3

💡 Hint

Look at the 'Send response' action in execution_table

If the password was missing in the request, what would happen?

A The server hashes the password anyway

B The server sends a 400 error and stops

C The server saves the user with empty password

D The server ignores the request

💡 Hint

Refer to step 2 in execution_table where input validation happens

Concept Snapshot

User registration flow in Express:
- Receive POST /register with username and password
- Validate inputs; if missing, send 400 error
- Check if user exists; if yes, send 409 error
- Hash password securely
- Save user data to database
- Send 201 success response
Always validate and hash before saving!

Full Transcript

This visual execution trace shows how a user registration request is handled in Express. First, the server receives a POST request with username and password. It checks if both are present; if not, it sends a 400 error. Then it checks if the username already exists in the database. If it does, it sends a 409 error. If not, it hashes the password securely, saves the new user to the database, and finally sends a 201 success response. Variables like username, password, exists, and hash change step-by-step as the code runs. This flow ensures safe and correct user registration.

Practice

1. What is the main purpose of using app.post('/register', ...) in an Express user registration flow?

easy

A. To update user details after registration

B. To serve the registration form HTML page

C. To handle incoming registration data sent by the client

D. To delete a user from the database

Solution

1. Step 1: Understand HTTP methods in Express

   app.post is used to handle POST requests, which usually send data to the server.

2. Step 2: Identify the role of the '/register' route

   The '/register' route is commonly used to receive new user data for account creation.

3. Final Answer:

   To handle incoming registration data sent by the client -> Option C

4. Quick Check:

   POST route = handle registration data [OK]

Hint: POST routes handle data sent from forms or clients [OK]

Common Mistakes:

• Confusing GET with POST for data submission
• Thinking app.post serves HTML pages
• Mixing update/delete operations with registration

2. Which of the following is the correct way to parse JSON data sent in a POST request in Express?

easy

A. app.use(express.urlencoded())

B. app.use(express.json())

C. app.get(express.json())

D. app.post(express.text())

Solution

1. Step 1: Identify middleware for JSON parsing

   Express provides express.json() middleware to parse JSON request bodies.

2. Step 2: Confirm correct usage

   It should be used with app.use() to apply globally or on specific routes.

3. Final Answer:

   app.use(express.json()) -> Option B

4. Quick Check:

   Use express.json() middleware for JSON data [OK]

Hint: Use express.json() to parse JSON POST data [OK]

Common Mistakes:

• Using express.urlencoded() for JSON data
• Calling express.json() inside app.get()
• Using express.text() for JSON parsing

3. Given the following Express route code for user registration, what will be the response if the user already exists?

app.post('/register', (req, res) => {
  const { username } = req.body;
  if (users.includes(username)) {
    res.status(400).send('User exists');
  } else {
    users.push(username);
    res.status(201).send('User created');
  }
});

medium

A. Status 201 with message 'User created'

B. Status 500 with message 'Server error'

C. Status 404 with message 'Not found'

D. Status 400 with message 'User exists'

Solution

1. Step 1: Check the condition for existing user

   The code checks if username is in users array and sends status 400 with 'User exists' if true.

2. Step 2: Understand response for existing user

   If the user exists, the response is a 400 status code with the message 'User exists'.

3. Final Answer:

   Status 400 with message 'User exists' -> Option D

4. Quick Check:

   User exists triggers 400 'User exists' [OK]

Hint: Check if user exists before adding to respond 400 [OK]

Common Mistakes:

• Assuming new user response for existing user
• Confusing status codes 400 and 201
• Ignoring the if condition logic

4. Identify the error in this Express user registration route:

app.post('/register', (req, res) => {
  const { username, password } = req.body;
  if (!username || !password) {
    res.status(400).send('Missing fields');
  }
  users.push({ username, password });
  res.status(201).send('User registered');
});

medium

A. Missing return after sending 400 response causes multiple responses

B. Incorrect HTTP method used; should be GET instead of POST

C. users.push should be outside the route handler

D. No error; code works correctly

Solution

1. Step 1: Analyze the if condition handling missing fields

   The code sends a 400 response if username or password is missing but does not stop execution.

2. Step 2: Identify consequence of missing return

   Without return, the code continues and tries to push user and send another response, causing an error.

3. Final Answer:

   Missing return after sending 400 response causes multiple responses -> Option A

4. Quick Check:

   Return after res.send to stop execution [OK]

Hint: Always return after sending response to avoid errors [OK]

Common Mistakes:

• Not returning after res.send in condition
• Using GET instead of POST for data submission
• Trying to push users outside route handler

5. You want to improve the user registration flow to prevent duplicate usernames and ensure passwords are at least 8 characters. Which code snippet correctly implements these checks before saving the user?

app.post('/register', (req, res) => {
  const { username, password } = req.body;
  // Your code here
});

hard

A. if (users.includes(username)) { res.status(400).send('User exists'); return; }
if (password.length < 8) { res.status(400).send('Password too short'); return; }
users.push({ username, password });
res.status(201).send('User registered');

B. if (!users.includes(username)) { res.status(400).send('User exists'); return; }
if (password.length > 8) { res.status(400).send('Password too short'); return; }
users.push({ username, password });
res.status(201).send('User registered');

C. if (users.includes(username)) { res.status(201).send('User exists'); return; }
if (password.length < 8) { res.status(201).send('Password too short'); return; }
users.push({ username, password });
res.status(400).send('User registered');

D. if (users.includes(username)) { res.status(400).send('User exists'); }
if (password.length < 8) { res.status(400).send('Password too short'); }
users.push({ username, password });
res.status(201).send('User registered');

Solution

1. Step 1: Check for existing username

   The code checks users.includes(username). If true, it responds with status 400 'User exists' and returns to prevent duplicates.

2. Step 2: Validate password length

   The code checks password.length < 8. If true, responds with 400 'Password too short' and returns.

3. Step 3: Add user and send success response

   After validations, users.push({ username, password }) and sends 201 'User registered'.

4. Final Answer:

   if (users.includes(username)) { res.status(400).send('User exists'); return; } if (password.length < 8) { res.status(400).send('Password too short'); return; } users.push({ username, password }); res.status(201).send('User registered'); -> Option A

5. Quick Check:

   Check user exists + password length, return on error [OK]

Hint: Return immediately after validation errors to stop flow [OK]

Common Mistakes:

• Not returning after sending error response
• Using wrong status codes for errors
• Adding user before validation checks