I built a tool to check and analyze Next.js website routes

Really experimental, but I noticed some Next.js deployments expose a buildManifest file that links every available route to its corresponding CSS and JS assets. As an experiment, I went a bit further and built a tool around it: nextr4y. The idea is to scan a target Next.js site and uncover internal routes – even protected or hidden ones (like authenticated pages) – straight from the manifest. You can then recreate how those pages look semi-automatically using agentic IDEs like Cursor. Still a bit rough and doesn’t handle every type of Next.js deployment (I pretty much built this over ~8 hours abusing LLMs in Cursor

Apr 22, 2025 - 02:47

I built a tool to check and analyze Next.js website routes

Really experimental, but I noticed some Next.js deployments expose a buildManifest file that links every available route to its corresponding CSS and JS assets.

As an experiment, I went a bit further and built a tool around it: nextr4y. The idea is to scan a target Next.js site and uncover internal routes – even protected or hidden ones (like authenticated pages) – straight from the manifest. You can then recreate how those pages look semi-automatically using agentic IDEs like Cursor.

Still a bit rough and doesn’t handle every type of Next.js deployment (I pretty much built this over ~8 hours abusing LLMs in Cursor