Feed and Detail

Goal

This snapshot advances Meridian Notes by teaching you to render a database feed and dynamic note detail routes.

Every numbered folder is a complete application. Run this stage on its own, then compare it with the previous snapshot to isolate the new responsibility.

Prerequisites

Use Node.js 20 or newer, npm, and a terminal. You should be comfortable with JavaScript functions, objects, modules, and basic HTML forms.

The development server uses port 3000. Data-backed snapshots use PostgreSQL on host port 5433 and keep their data in a database unique to that folder.

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

Concepts

A collection route and a dynamic [id] route perform different reads. notFound() stops rendering and returns the framework's 404 response.

Keep the server boundary visible: Server Components may read trusted data directly, while Server Actions and route handlers must validate all incoming values and re-check authorization.

Walkthrough

Link every feed card to its id route, load the post with its author, and handle an id that does not exist.

Trace the example from request to rendered result, then inspect the matching snapshot for its surrounding types, validation, error handling, and configuration.

const post = await prisma.post.findUnique({ where: { id }, include: { author: true } });
if (!post) notFound();

Run and verify

Enter 05-Feed-And-Detail, install its dependencies, and copy .env.example when the snapshot includes one.

Open http://localhost:3000. Keep the terminal visible so framework, Prisma, and authentication errors can be matched to the browser action that caused them.

git clone https://github.com/michaeldunga1/fcc-nextjs-blog.git
cd fcc-nextjs-blog/05-Feed-And-Detail
npm install
cp .env.example .env
docker compose -f ../docker-compose.yml up -d
npm run db:migrate
npm run db:seed
npm run dev

Troubleshooting

Await params in current App Router pages. If Prisma throws, separate an invalid connection from a valid query that returned null.

A missing-module error usually means npm ran in another snapshot. Database errors often mean Docker is stopped, the environment file is missing, or this folder points at the wrong numbered database.

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

Try this

Show the publication date on feed cards and detail pages.

Test one expected path and one invalid or unauthorized path. A production-minded app gives useful feedback without exposing secrets or stack traces.

• Make one focused change
• Verify it in the browser
• Continue only after this snapshot works