why to create local one? what I want to test the remote d1 on local ?
why to create local one? what I want to test the remote d1 on local ?
H
Wdaaamn, was this supposed to be a feature ? why ?
SI think I've figured out what's helping our next on pages worker bundle go over 25MiB.
We have 1256 static pages and 24 edge function routes.
The static routes are all output to a prerender-manifest.json (this is normal NextJS behaviour).
The next-on-pages deploy process copies the contents of this file into each edge function js file as a __PRERENDER_MANIFEST variable.
Our prerender-manifest.json comes in at 781KiB, so for me we've got it duplicated 24 times and in theory only need 1 copy of this in the final worker that's generated.
Has anyone else come across this before I raise it as a bug/improvement on GitHub?
We have 1256 static pages and 24 edge function routes.
The static routes are all output to a prerender-manifest.json (this is normal NextJS behaviour).
The next-on-pages deploy process copies the contents of this file into each edge function js file as a __PRERENDER_MANIFEST variable.
Our prerender-manifest.json comes in at 781KiB, so for me we've got it duplicated 24 times and in theory only need 1 copy of this in the final worker that's generated.
Has anyone else come across this before I raise it as a bug/improvement on GitHub?
Aany differences between 1.9.0 and 1.13.2 that would give me an "ReferenceError: XMLHttpRequest is not defined"
K"Your Worker exceeded the size limit of 1 MiB"
How? I tried already quite a few thing in my my nextjs 14 app. This is the app:
How? I tried already quite a few thing in my my nextjs 14 app. This is the app:
AGoing to try 1.12.1.. i wonder what version killed this
Ayea 1.9.0 is the last version of next-on-pages i can use.. Tips for troubleshooting would be appreciated
Ahttps://github.com/cloudflare/next-on-pages/releases/tag/%40cloudflare%2Fnext-on-pages%401.10.0 no obvious changes
GitHub
Minor Changes
739e2a7: make (no-op) caches available in dev mode
update setupDevPlatform to also add a caches object to the global scope
so that it can be used during development in a production-...
739e2a7: make (no-op) caches available in dev mode
update setupDevPlatform to also add a caches object to the global scope
so that it can be used during development in a production-...
YApparently 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
