Instead, dev resolves to a 400 error and prod resolves to a 500. You won't see this because the app throws an error: I expect no un-decodable entities at all to cause a 500 error. This gets picked up by error-logging apparatuses, causing noise. Dynamic Routes, Error Handling

TL;DR

The issue can be addressed by properly handling or escaping un-decodable entities in dynamic route slugs, potentially through Next.js configuration or custom routing logic.

Guidance

• Investigate Next.js routing configuration options to handle special characters in slugs, such as using a custom getStaticPaths function or adjusting the router settings.
• Consider implementing a middleware or a custom routing solution to catch and handle un-decodable entities before they cause errors.
• Review the next.config.js file for any existing configurations that might be contributing to the issue, such as trailingSlash or basePath settings.
• Look into using a library or utility function to properly encode or decode URL slugs, ensuring that un-decodable entities are handled gracefully.

Example

No specific code example can be provided without further details on the desired handling of un-decodable entities. However, a potential approach might involve creating a custom middleware function to preprocess route slugs and handle special characters.

Notes

The provided environment information and package versions may be relevant to the issue, but without more specific details on the desired behavior, it's challenging to provide a precise solution. The use of a canary version of Next.js (16.2.1-canary.26) might also be a factor, and checking the official Next.js documentation or issue tracker for similar problems could be helpful.

Recommendation

Apply a workaround by implementing custom routing logic or middleware to handle un-decodable entities, as upgrading to a fixed version is not explicitly implied in the issue description. This approach allows for a targeted solution without relying on potential fixes in future versions of Next.js.