Routing

Goal

This snapshot advances Harborline Digest by teaching you to organize page routes.

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 Docker for Postgres stages.

Port 3003 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

Routes map URLs to handlers or pages.

Keep server routes thin: pages present data, server handlers enforce rules, and templates escape output by default.

Walkthrough

Add home, about, and health routes.

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

definePageMeta({ path: '/about' })

Run and verify

Enter 02-Routing, install dependencies, copy .env.example, and start Nuxt on port 3003.

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

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

Troubleshooting

A missing route registration leaves the path undefined.

For database failures, confirm Docker/Wrangler and the harborline_NN name when applicable. Never commit .env or node_modules.

• Read the first error first
• Restart after environment changes
• Never commit secrets

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