nextjs - 💡(How to fix) Fix [bug] Prefixing dynamic path segments on redirects breaks typedRoutes, generating static routes instead of dynamic routes [1 comments, 2 participants]

TL;DR

The issue can be addressed by modifying the redirects function in next.config.js to correctly handle dynamic path segments.

Guidance

• Review the redirects function to ensure that dynamic path segments are properly defined, potentially by using a regex pattern to match the dynamic segment.
• Verify that the typedRoutes option is enabled, as it is required for correct type generation.
• Check the Next.js documentation for any updates or changes to the redirects function or typedRoutes option.
• Consider testing with a simplified redirects function to isolate the issue.

Example

redirects() {
  return [
    {
      source: /^\/c:(\d+)$/, // using regex to match dynamic segment
      destination: "/dashboard/customers/:id",
      permanent: true,
    },
    {
      source: /^\/p:(\d+)$/, // using regex to match dynamic segment
      destination: "/dashboard/products/:id",
      permanent: true,
    },
  ];
},

Notes

The provided example code snippet is a potential solution, but it may require further modification to fit the specific use case. Additionally, the issue may be related to a bug in the Next.js version being used, and upgrading to a newer version may resolve the issue.

Recommendation

Apply workaround: The issue can be addressed by modifying the redirects function to correctly handle dynamic path segments, as shown in the example code snippet. This workaround allows for correct type generation and routing.