Password Reset

View saved

Goal

This snapshot advances Tidepool Notes by teaching you to issue expiring one-use password reset tokens.

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

Store a random token and expiry on the user. Locally print the link to the console instead of requiring SMTP.

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

Walkthrough

Create a forgot-password action, save a token, and complete the reset only when the token is valid and unexpired.

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

resetToken: randomBytes(24).toString("hex")
console.log("[mail]", link)

Run and verify

Enter 11-Password-Reset, 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.

docker compose -f ../docker-compose.yml up -d
git clone https://github.com/michaeldunga1/fcc-remix-blog.git
cd fcc-remix-blog/11-Password-Reset
npm install
cp .env.example .env
npm run db:push
npm run db:seed
npm run dev

Troubleshooting

Always show a generic success message so attackers cannot probe which emails exist.

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

Request a reset for Ada and complete it from the console link.

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

Next: Deploy

Comments

One comment per signed-in account. Comments are saved with this page’s URL.