Timers

This lesson covers Timers. Think of this lesson as a short workshop you can run on your laptop.

What you will learn

• What timers 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: Async/Await — Complete Guide

Explain it simply

Timers let you run code later (setTimeout) or on a repeat (setInterval). Node uses them for delays, polling, and scheduled jobs.

Why developers use this

• Node stays fast under load
• Required for files and databases
• Common in interviews

How it works (step by step)

1. Your code starts a task (read file, query DB, timer).
2. Node continues other work instead of waiting idle.
3. When the task finishes, your callback, Promise, or await runs.
4. Errors go in catch or .catch() — never ignore them.

Code example — type this yourself

setTimeout(() => console.log('After 1 second'), 1000);
const id = setInterval(() => console.log('tick'), 500);
setTimeout(() => clearInterval(id), 2500);

clearInterval stops the repeat. Timers are handled by the event loop — they do not block other code.

What each part does

• setTimeout(() => console.log('After 1 second'), 1000); — Prints to the terminal — great for learning; use proper logging in production.
• const id = setInterval(() => console.log('tick'), 500); — Prints to the terminal — great for learning; use proper logging in production.
• setTimeout(() => clearInterval(id), 2500); — Line 3: runs as written.

Real life: where Timers shows up

An online store uses Timers so hundreds of users can check order status at once. While one request waits for the database, Node handles other users instead of freezing. Start small: one feature working beats a perfect architecture on paper.

Try it yourself — hands-on

1. Create a new file (e.g. timers-demo.js) in an empty folder
2. Type the example code for Timers 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 — Timers only feels easy after you run code yourself.

Interview note

Interviewers often ask: “What is Timers?” Answer in one sentence, then give a tiny example you actually ran.

Summary

• You can explain Timers 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