Routing

Goal

This snapshot advances Circuit Daily by teaching you to organize page routes with Nest controllers.

Every numbered folder is a complete app. Run this stage independently, then compare it with the previous folder.

Prerequisites

Use Node.js 20+, npm, and a terminal. You should recognize TypeScript modules, decorators, and HTTP verbs.

Port 3001 must be free. Copy .env.example before starting database stages.

• Node.js and npm
• A code editor and terminal
• Docker from part 4 onward

Concepts

Controllers group related endpoints. Decorators declare methods and paths; modules wire providers.

Keep controllers thin: accept input, call services, render Handlebars views. Escape stays on by default in templates.

Walkthrough

Add home, about, and health handlers on the app controller.

Read the example, then open the matching snapshot. The repository includes the surrounding setup and error handling.

@Controller()
export class AppController {
  @Get('about') about() { return 'About Circuit Daily'; }
}

Run and verify

Enter 02-Routing, install dependencies, copy .env.example when present, and start Nest on port 3001.

Open http://127.0.0.1:3001. Watch the terminal for validation and database errors.

git clone https://github.com/michaeldunga1/fcc-nestjs-blog.git
cd fcc-nestjs-blog/02-Routing
npm install
cp .env.example .env
npm run start:dev

Troubleshooting

A missing module import leaves controllers undefined. Check both path and HTTP method.

Missing-module errors usually mean npm install ran in another snapshot. For Postgres failures, confirm Docker and the circuit_NN database name.

• Read the first error first
• Restart after environment changes
• Never commit .env or node_modules

Try this

Add a /contact plain-text route.

Test a happy path and one invalid or unauthorized request.

• Make one small change
• Test it in the browser
• Compare with the next snapshot only after it works