web-platform-conventions

Fix Next.js 16+ middleware build errors by migrating auth, redirects, and header logic from the deprecated middleware.ts to the mandated proxy.ts file for edge request handling.

Configure Content-Security-Policy headers for third-party SDKs by adding the SDK's network origin to the strict CSP connect-src or script-src directives to prevent XSS and data exfiltration risks.

Enforce strict network origin gating in Next.js by applying security-first Content-Security-Policy rules that restrict unauthorized network access across all web frontend code and edge logic.

Use proxy.ts instead of middleware.ts in Next.js 16+ because middleware is deprecated for edge code, and proxy.ts ensures consistent adherence for auth and redirect logic without build errors.

Yes, this approach supports structured logging adherence by standardizing web platform conventions across edge request handling, proxy.ts usage, and frontend security configurations.

Yes, use proxy.ts for handling edge requests and header updates in a web frontend to eliminate deprecated middleware usage and maintain consistent Next.js 16+ build stability.