chore(open-next): use proxy.ts instead of middleware.ts

.github/CODEOWNERS

@@ -15,7 +15,7 @@ pnpm-lock.yaml @nodejs/web-infra
 # Framework
 apps/site/next.config.mjs @nodejs/web-infra
 apps/site/next.dynamic.mjs @nodejs/web-infra
-apps/site/middleware.ts @nodejs/web-infra
+apps/site/proxy.ts @nodejs/web-infra
 apps/site/navigation.mjs @nodejs/web-infra
 apps/site/playwright.config.mjs @nodejs/web-infra
 

apps/site/middleware.ts → apps/site/proxy.ts

@@ -16,6 +16,6 @@ export default createMiddleware({
   alternateLinks: false,
 });
 
-// We only want the middleware to run on the `/` route
+// We only want the proxy to run on the `/` route
 // to redirect users to their preferred locale
 export const config = { matcher: ['/'] };

docs/technologies.md

@@ -204,7 +204,7 @@ We use a custom i18n solution because:
 
 #### Locale Detection and Routing
 
-- `next.middleware.js`: Handles browser locale detection and redirects
+- `proxy.ts`: Handles browser locale detection and redirects
 - Falls back to `/en` for unsupported locales
 - Provides seamless user experience across languages
 

platforms/cloudflare/package.json

@@ -18,7 +18,7 @@
   },
   "dependencies": {
     "@flarelabs-net/wrangler-build-time-fs-assets-polyfilling": "^0.0.1",
-    "@opennextjs/cloudflare": "^1.20.2",
+    "@opennextjs/cloudflare": "^1.20.10",
     "@sentry/cloudflare": "^10.68.0",
     "@typescript/vfs": "^1.6.4",
     "twoslash": "^0.3.9",