Route config with `edge` runtime not respected.
Answered
Sloth bear posted this in #help-forum
Sloth bearOP
I wanna use more the
Also when I check the logs it's still a normal "lambda" 🤔 Any idea if this is a known bug?
edge runtime in my pages config. However, when I build I see everything as ƒ (Dynamic) server-rendered on demand. I think they used to show another symbol.Also when I check the logs it's still a normal "lambda" 🤔 Any idea if this is a known bug?
Answered by joulev
the build log is a recent change, they now merge nodejs runtime and edge runtime into one single log type, not separate like before.
if you deploy on vercel, you can still verify that your pages are rendered in the edge runtime normally like here.
if you deploy on vercel, you can still verify that your pages are rendered in the edge runtime normally like here.
2 Replies
@Sloth bear I wanna use more the `edge` runtime in my pages config. However, when I build I see everything as `ƒ (Dynamic) server-rendered on demand`. I think they used to show another symbol.
Also when I check the logs it's still a normal "lambda" 🤔 Any idea if this is a known bug?
the build log is a recent change, they now merge nodejs runtime and edge runtime into one single log type, not separate like before.
if you deploy on vercel, you can still verify that your pages are rendered in the edge runtime normally like here.
if you deploy on vercel, you can still verify that your pages are rendered in the edge runtime normally like here.
Answer
Sloth bearOP
Ah thank you 🙏 Not sure what my eyes saw in the logs, but now I can see indeed the logs from edge! Thanks!