DEDUPED Hot AI repos. Real use cases. What people build. Get the Monday 5

How to find every page a shared React component change reaches with Farol

Use Farol's React Router recipe to list the pages a change touches before you merge.

Short answer: cd into the React app; then run echo '{ "routes": { "file": "src/routes.tsx" } }' > farol.config.json; run npx @winninjs/farol routes to list your pages. All steps.

Who it is forA frontend developer changing a shared hook or component used across many pages.

The problemA one-line change to a shared hook can break dozens of pages nobody thought to test.

The outcomeA list of every page the change reaches, with the call chain, so you test the right ones by hand.

What you need first

  • Node.js 22+ and git
  • go for Go projects, python3 3.11+ for Python projects
  • Optional: coverage, lint and audit reports from your CI

Steps

  1. cd into the React app
  2. Run echo '{ "routes": { "file": "src/routes.tsx" } }' > farol.config.json
  3. Run npx @winninjs/farol routes to list your pages
  4. Check out your feature branch and run the analyze and html commands
  5. Mark pages behind a feature flag in the report and tick files as reviewed to watch the risk drop

Prompt for your agent

Configure winnin/farol for this React Router app, analyze <branch>, and list every page the change reaches with its call chain so I know what to test by hand.

Caveat.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for winnin/farol and "Find every page a shared React component change reaches"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer