[codex] migrate ElinksNet to Next.js and HeroUI

[ElinksTeam]

What changed

• Migrated the active frontend from Vue/Vite to React 19, Next.js App Router, Tailwind CSS 4, shadcn/ui, and HeroUI v3.
• Restored fused IP intelligence, proxy risk, Groq AI analysis, connectivity, WebRTC, DNS leak, speed test, and JSON report export.
• Restored Globalping latency/MTR/censorship measurements, DNS resolver, RDAP/WHOIS, MAC lookup, proxy rule matrix, browser fingerprint, security checklist, invisibility report, CLI, Docker guide, and service status.
• Consolidated backend operations into four dynamic Next.js routes to stay below the Vercel Hobby serverless-function limit.
• Restored PWA registration with static-only caching; API responses are explicitly excluded.

Why

The initial framework migration replaced the Vue application but left advanced tool pages as placeholders. This update ports their user-facing workflows and service integrations to React while keeping provider credentials server-side.

Impact

All primary network diagnostics are usable in the Next.js interface. Public endpoints are rate limited, validate input, use upstream timeouts, and avoid exposing private API keys.

Validation

• npm run check
• npm audit --audit-level=moderate — 0 vulnerabilities
• Live DNS queries across four DoH providers
• Live RDAP and MAC vendor lookups
• Live Globalping measurement with 16 regional results
• Desktop and 390 px mobile browser verification with no runtime errors

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
my-ip	Ready	Preview, Comment	Jul 2, 2026 8:11pm