Routing

Goal

This snapshot advances Tidepool Notes by teaching you to organize pages with Remix file-based 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 a terminal. You should recognize React components, TypeScript modules, and HTTP verbs.

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

Each route module can export a loader, action, and default component. Nested URLs come from dotted filenames and folders.

Keep the server boundary visible: Remix loaders read trusted data on the server; actions must validate input and re-check authorization before mutations.

Walkthrough

Add home, about, and health routes; link them with Remix Link.

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

<Link to="/about">About</Link>

Run and verify

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

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

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

Troubleshooting

Route filenames are case-sensitive on Linux. Confirm each route exports a default component.

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

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

Try this

Add a /health resource route that returns JSON ok: true.

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