Apparently the issue starts from 1.31.2 with the route scoping change, 1.31.1 should work without i
Apparently the issue starts from 1.31.2 with the route scoping change, 1.31.1 should work without issue
AI tried on 1.10.0 and had the same issue
Aits not apparently obvious what the change was. i wonder if its a dep change..
AI think its probably an unintended interaction with graphql-request
Jhmm we dedupe some of these manifests but this might be a new one that we aren't accounting for, could you make an issue please
Jyeah your XMLHttpRequest problems sounds like an issue with one of your dependencies to me
SSure,
SGitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030 CP...
J"UnhandledSchemeError: Reading from "node:crypto" is not handled by plugins" anyone else experienced that error locally when building? I have following import: 'import { randomUUID } from 'node:crypto';' as mentioned on: https://developers.cloudflare.com/workers/runtime-apis/nodejs. Am I doing something wrong?
JIs that error coming when Next.js builds?
J@Anay-208 you can, you just need to import it from node:crypto -> https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/
Cloudflare Docs
The node:crypto module provides cryptographic functionality that includes a set of wrappers for OpenSSL’s hash, HMAC, cipher, decipher, sign, and verify functions.
JThat's causing the build issue, they also discussed it internally at: https://github.com/replicate/replicate-javascript/issues/225 I am now using the web crypro api which should also work inside a worked as you said (still need to verify 
)
)GitHub
Environment: Node Version: 20.11.1 macOS: 14.2.1 next: 14.1.3 replicate: 0.28.1 I am getting Module build failed: UnhandledSchemeError: Reading from "node:crypto" is not handled by plugin...
Jyeah webcrypto should be fine
DHi, I have another question about Cloudflare Pages. Whenever I uploaded changes on Github to the appropriate branch it would automatically build the app and upload it to Pages, but for some time now (2 weeks) the app doesn't build, it stutters and hangs like that until timeout. When I do it manually using a command from the console, everything uploads nicely in 2-3 minutes (the app is on NextJS)
DThere is nothing in the logs, it just stutters at random times
Dmessage.txt7.42KB
DWhen by some miracle the upload succeeds, the beginning of the logs looks the same as this one there
Dany ideas?
BHey! I'm trying to build a nextjs project to Pages for the first time, but building with next-on-pages fails on:
I haven't experienced this on other next projects on Pages, I saw some open Github issues (but also lots resolved) and I just can't get it to work. It's 100% App Router, there's no global-error.tsx, not-found.tsx or whatever error.tsx.
Does anyone stumbled on this issue before?
I haven't experienced this on other next projects on Pages, I saw some open Github issues (but also lots resolved) and I just can't get it to work. It's 100% App Router, there's no global-error.tsx, not-found.tsx or whatever error.tsx.
Does anyone stumbled on this issue before?
Disn't the not-found.tsx generated automatically by next-on-pages?
BYep I think so, or at least the vercel cli
BI created a custom one instead and it fixed the issue 
Jyeah vercel incorrectly generates this function which never seems to be used
Banother app of mine that's running fine doesn't have this issue, same setup basically
Bweird
Bnot having my day at all either 
B
Bfighting this one, no way this app is 60MB
Jthat's crazy large
Bwhen building without next-on-pages, the largest page is basically 17kB, most are 3-5kB
Band that's the size reported by nextjs
Bnot the first load js also
Band in the CF Pages logs, it shows >1MB for all pages basically
B
Bbundle analyzer shows a huge chunk, but no way it's over 60MB
Yhello
if i have a nextjs api deployed on cloudflare pages
if a UNIQUE user makes an api request, it is guaranteed to be executed only ONCE on the closest edge runtime right?
if i have a nextjs api deployed on cloudflare pages
if a UNIQUE user makes an api request, it is guaranteed to be executed only ONCE on the closest edge runtime right?
Ybased on my understanding of cloudflare pages & nextjs edge runtimes, they're all distributed across the world
IA request will trigger on the edge runtime once, if that's what you mean.
IIf they make multiple requests it will trigger multiple times.
Jbundle analyzer wont be very useful i dont think, since its a bit different to the final worker
BYep fair enough
BNot sure where to start to debug this tbh,I’m happy to help figure out what’s going on 
AIf I have trouble adding a new website to Cloudflare, where do I look for a solution?
A
