Ea/fix middleware issue

[ErnestM1234]

No description provided.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
gt-docs	Ready	Preview	Comment	Aug 29, 2025 5:44pm

5 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
example-ai-chatbot	Ignored			Aug 29, 2025 5:44pm
example-create-react-app	Ignored			Aug 29, 2025 5:44pm
example-gt-next-starter	Ignored			Aug 29, 2025 5:44pm
example-next-create-app	Ignored			Aug 29, 2025 5:44pm
example-vite-create-app	Ignored			Aug 29, 2025 5:44pm

[greptile-apps]

Greptile Summary

This PR addresses middleware-related issues with locale detection during Static Site Generation (SSG) in Next.js applications using General Translation. The core problem being fixed is that SSG disrupts locale resolution because Next.js request APIs (headers() and cookies()) are not available during build time.

The changes introduce several key improvements:

1. Custom getLocale Support: Enables users to provide their own locale detection logic for SSG scenarios through a new configuration option and webpack aliasing system.

2. Version-Aware Next.js Compatibility: Implements detection logic for different Next.js versions (15.1-15.4 uses unstable_rootParams, 15.5+ uses experimental next/root-params) to handle the evolving root parameters API.

3. Enhanced Error Handling: Adds specific error messages that guide users to SSG documentation when locale determination fails, replacing generic errors with actionable guidance.

4. Request Access Detection: Introduces utility functions to detect when Next.js request APIs are available before attempting to use them, preventing crashes during static generation.

5. Documentation Updates: Adds comprehensive SSG documentation with version-specific implementation examples for custom locale resolution.

The solution maintains backward compatibility while providing a clear upgrade path for users experiencing locale detection issues in SSG environments. The changes integrate across multiple packages (next, docs) and include proper TypeScript support and webpack configuration.

Confidence score: 2/5

• This PR addresses a legitimate issue but contains several implementation problems that could cause runtime failures
• Score lowered due to critical logic errors in version comparison, potential silent failures in async imports, and inconsistent locale validation paths
• Pay close attention to packages/next/src/plugin/getStableNextVersionInfo.ts and packages/next/src/next/detectRequestAccess.ts for logic errors

_{9 files reviewed, 8 comments}

_{Edit Code Review Bot Settings | Greptile}