Edge Functions cause 500 Error with [email protected]

[lidqqq]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

on Vercel, the runtime is Node.js v14

What browser are you using? (if relevant)

Chrome Chrome 98.0.4758.102 (Official Build) (arm64)

How are you deploying your application? (if relevant)

Vercel

Describe the Bug

I ran into a bug about Edge Functions with [email protected].
Edge Function causes a 500 error on Vercel, but local development doesn't cause them. So you can find them only when you deploy to Vercel so far.

https://ab-testing-simple-12-1.vercel.app/

And canary version causes it too

https://ab-testing-simple-canary.vercel.app/

But it works correctly with [email protected]
https://ab-testing-simple-12-0-x.vercel.app/

I got the same bug on my other production project that Edge Functions uses. Perhaps all of the Edge Functions cause 500 error regardless of how they use.

Expected Behavior

behave as well as the before versions such as [email protected]
https://ab-testing-simple-12-0-x.vercel.app/

To Reproduce

• go example repository of edge function
• deploy to vercel
• change Next.js version to v12.1
• push remote and go production url

Or you can use these repositories that I used for my research

cause 500 error after v12.1

https://github.com/lidqqq/ab-testing-simple-12.1
https://github.com/lidqqq/ab-testing-simple-canary

works correctly

https://github.com/lidqqq/ab-testing-simple-12.0.x

[balazsorban44]

Hi, thank you for reporting this!

I could identify the problem and mentioned it to the relevant team. Luckily, this is not a bug in Next.js, only that our examples should be updated to reflect #33410.

You should see an error in your Vercel Dashboard that points to this page:
https://nextjs.org/docs/messages/middleware-relative-urls#possible-ways-to-fix-it

I deployed a version that works here: https://balazsorban-34566-balazsorban.vercel.app/

The code changes needed are in the two _middleware files respectively:

const destination = req.nextUrl.clone()
destination.pathname = `/home/${bucket}` // or /marketing
const res = NextResponse.rewrite(destination)

[lidqqq]

@balazsorban44 Thanks for replying and investigating 🙏
I got it, and I opened the PR so please check it when you have some time 👍

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.