Bseems like you are using axios on edge runtime
Bmaybe not use axios ? and use
requestly or some modern fetch library
AI agree, which is why i'm confused. but the only thing I'm changing is the version of next-on-pages
Ait makes me wonder if there is a dependency interaction that i'm not aware of
Athe actual code change that made this work.. Tho the package.json change is massive
Aremoving this line, or changing the version starts producing the XMLHttpRequest
Ayea. line change with that add on is +10354 -3237
Bare you using axios or not?
Anot directly, and i dont see it in any sub dependencies
Amost everything is through a graphql library that could use axios, but has an override to use fetch
Aaxios does not appear in the package.lock
Bwhat about cross-fetch ?
Aindeed it does
Byeah that could be the cause, is there a way you can initiate a graphql client using your own fetch?
Bit should have options
Ayea you can override the fetch in the graphql client. if i dont do that it doesnt work on any version of next-on-pages
Arequired by node_modules/fbjs "node_modules/graphql-request":
Anot familiar with fbjs, hmm
Anot sure this explains why changing the next-on-pages version breaks this either
Jmaybe it's updating other dependencies that aren't locked to specific patches too
BThere is a fix coming to next-on-pages, so sentry will be implemented soon. I dont know when the next release date is
Ayea i'm wondering about that. its weird because if i changee this to the 1.10 or later it breaks, and then back it works.. just need to trace every dep i guess
BNice
MIf bundle size is the issue, I think take a look at posthog - it's quite nice pricing wise and I think offers a somewhat similar service
Ai wonder if there is a way to tell it to ignore the cross-fetch library.. it may be stealing the 'fetch' word, and not doing a good job on cloudflare
Ajust tried the 4.0 version of that lib which claims cf support, with no go
Bdoes it work on next-on-pages?
AHuh, if cross-fetch is an included package in my project, 'fetch' gets overwritten globally somehow if I'm using a specific combination of packages.. regardless if I import cross-fetch in my specific file.
Afeels like a build problem, tho, is there a reference somewhere to the original fetch i can use?
Atho i wonder if i can do some next.config.js magic and tell it to use a local file for cross-fetch package
A
Ait went a little sideways
Lhello im getting this error, someone knows whats happend?
server side exception and when check logs
"logs": [
{
"message": [
"Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
],
server side exception and when check logs
"logs": [
{
"message": [
"Error: The 'cache' field on 'RequestInitializerDict' is not implemented."
],
SThis might be more of an nextjs issue then next-on-pages, but I randomly started getting this error:
SSThe thing is, I don't have a not-found page
SI can see that previously in the build log it appeared as this
SSand that produced successful builds
Sbut now it's
S
Ehi everyone
Eis there someone that can help me creating a dynamic page? when i create a folder and add a [id].tsx file inside, i can't make it work
KYou can just make a not found page with the edge runtime, I ran in to that issue when my root layout page was needing the edge runtime
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/troubleshooting/#app-router
https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/troubleshooting/#app-router
SThat's exactly what happened, thanks!
SIs there a way to just force edge runtime for functions globally?
KNo idea, not that I know of anyway
Jall routes under a layout will use the runtime specified in the layout
