nextjs - 💡(How to fix) Fix Middleware not triggered with node runtime + basePath [1 participants]

TL;DR

The issue can likely be resolved by updating the Next.js configuration to correctly handle middleware execution on Vercel.

Guidance

• Verify that the basePath configuration is correctly set in the Next.js config file, as this might affect how middleware is executed.
• Check the Vercel documentation for any specific requirements or restrictions on using middleware with Next.js, as the issue only occurs on Vercel deployment.
• Consider upgrading to the latest canary version of Next.js (15.6.0-canary.12) as suggested in the environment information, although this is not directly implied as the solution.
• Review the middleware code and configuration to ensure it is correctly set up to handle requests starting with the /us path.

Example

No specific code example can be provided without more details on the middleware implementation.

Notes

The issue seems to be related to the deployment on Vercel, as it works fine locally. This suggests that the problem might be related to the specific configuration or environment of Vercel.

Recommendation

Apply workaround: Since the issue is specific to Vercel deployment and the exact cause is not clear, trying to adjust the Next.js configuration or middleware setup to accommodate Vercel's requirements might be the most straightforward approach. Upgrading Next.js to the latest canary version could also be considered, but its direct impact on this issue is uncertain.