Correct way to implement _redirects file functionality for a Pages project using Next edge runtime?

Hi there, I've seen in a previous post that SvelteKit and _redirects seem ot be incompatible. I am experiencing this issue on my own Pages site unfortunately, and I'm wondering if Cloudflare has any guidance on a correct solution.

I don't necessarily need the _redirects file to live in my repo. I'm happy to use a different Cloudflare product for managing this, I'm just not sure which one would be the simplest to maintain and implement.

Thanks!

Previous post: Proxy error when trying to redirect to external url

James•6/13/23, 8:38 AM

I've not tried using _redirects with Next (you'd need to create the file in the output directory after build), but perhaps another way could be the next.config.js redirects option?

HareBearOP•6/13/23, 2:24 PM

Thanks @5927 , will try the next redirects.

Unfortunately, even though Cloudflare shows the parsed _redirects file for the deployment, they don't seem to work. The linked post seems to hint at routes handled by workers in edge runtime mode not having redirects applied.

Correct way to implement _redirects file functionality for a Pages project using Next edge runtime?

Similar Threads

Similar Threads

Similar Threads