nextjs - 💡(How to fix) Fix Proxy negative matching not working when using i18n config on Vercel [4 comments, 3 participants]

TL;DR

• The issue with the proxy matcher not working as expected on Vercel deployment can be addressed by adjusting the next.config.js file to properly handle internationalization (i18n) and middleware configuration.

Guidance

• Review the next.config.js file to ensure that the i18n configuration is correctly set up and does not interfere with the proxy matcher.
• Verify that the middleware configuration is properly defined and exported in the next.config.js file.
• Check the Vercel deployment configuration to ensure that it is correctly set up to handle the i18n and middleware configurations.
• Consider testing the deployment on a preview environment before deploying to production to catch any potential issues.

Example

// next.config.js
const nextConfig = {
  // ... other configurations ...
  i18n: {
    locales: ['en-US', 'pt-BR'],
    defaultLocale: 'en-US',
  },
  // Ensure middleware is correctly configured and exported
  experimental: {
    middleware: true,
  },
};

export default nextConfig;

Notes

• The issue seems to be related to the interaction between the i18n configuration and the proxy matcher, and adjusting the next.config.js file may resolve the issue.
• The fact that the issue only occurs on Vercel deployment and not in the local dev environment suggests that there may be a configuration or environment-specific issue at play.

Recommendation

• Apply workaround: Adjust the next.config.js file to properly handle i18n and middleware configurations, and test the deployment on a preview environment before deploying to production. This should help resolve the issue with the proxy matcher not working as expected on Vercel deployment.