nextjs - 💡(How to fix) Fix Link to the code that reproduces this issue [1 comments, 2 participants]

TL;DR

• Verify the base path configuration in Next.js to ensure it's correctly prefixing the base path for all requests.

Guidance

• Check the basePath option in the Next.js configuration file to ensure it's set correctly.
• Verify that the basePath is being applied consistently across all requests, including those for /__nextjs_original-stack-frames.
• Review the Next.js documentation for hosting at a base path to ensure the configuration is correct.
• Test the application with different request paths to identify any patterns or inconsistencies in base path prefixing.

Example

No specific code example can be provided without more context, but reviewing the Next.js configuration file (e.g., next.config.js) for the basePath setting is a good starting point.

Notes

The issue seems to be related to inconsistent base path prefixing in Next.js when hosting at a base path. Without more specific details about the configuration or code, it's challenging to provide a precise fix.

Recommendation

• Apply workaround: Review and adjust the base path configuration in Next.js to ensure consistent prefixing across all requests, as this seems to be the most direct approach to addressing the issue described.