NextJS redirects/rewrites regression on new runtime?

Support
,
1

Main Site Name: goboat-website-denmark
Main Site URL: Boat rental in Copenhagen, Aarhus, Odense. Book now! - GoBoat Denmark

Hi,

We’re upgrading from Next.js v12 to v14, and it seems that the rewrites in our _redirects file are no longer being applied.

Current _redirects Syntax:

/graphql https://some-api.io/graphql 200!
/api-gateway/graphql https://another-api.io/graphql 200!

We’ve tried both with and without the ! at the end.

Observations:

  • Using @netlify/plugin-nextjs@4.41.3 with Next.js v12:
    In the deploy summary, Netlify reports “XXX redirect rules processed,” with a base count of 96 redirects (from _redirects), even when no dynamic redirects are fetched. Both the dynamic redirects and _redirects file rewrites work as expected.
  • Using @netlify/plugin-nextjs@5.8.0 with Next.js v14.2.13:
    Netlify now reports “No redirect rules processed” in the deploy summary. The dynamic redirects specified in next.config.js work as expected, but rewrites in _redirects do not work.

We use both a netlify.toml file (without redirects) and a _redirects file. The _redirects file is programmatically placed in the .next folder after running next build using a custom script, which is still running as expected after the upgrade. We use this setup since netlify.toml does not support environment-specific redirects.

Could you assist with this issue?

Thank you!

3

We’ve followed up on this request in our helpdesk, feel free to continue correspondence there.