Dok.... I'll have to have a look 
, I wonder if the new entrypoints could have broken the next-dev servicing bindings (it could work with an older version of wrangler?)
, I wonder if the new entrypoints could have broken the next-dev servicing bindings (it could work with an older version of wrangler?)
Nremove this
Ni guess this
DD(to try to make help people avoid the pitfall of
.env and process.env)
BGood 
0anyone getting this error trying to deploy on cf pages?
0for some reason it keeps giving 500 internal error
W
Nsame here
RGitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:41 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8103 C...
Rhey, my supplier has invited me to access CF account where my DNS is hosted, however when i log in, I dont have the DNS zone option on the left ?
0ahh i see okok thanks
TI deploy my nextjs to Pages: here is the metric for the functions. It keeps saying "Exceeded CPU limit". what is the possible solution here, should I upgrade to Worker paid with has maximum 30s CPU time per invocation.
TI use unpdf to processing the pdf with that pages
Nyou should
Nor try another library that might do it faster
T@nob my use case is get a pdf from a client and parse it to extract the text from the pdf. Inittialt I try with popular library pdfjs-dist but it is not compatible with Workers so the only solution now is UnPDF which is a likely modified of pdfjs-dist for worker runtime
Acomplains about a _not-found file even if you dont have one.. interesting
Nyes you should buy the worker paid plan then
Ntrying to use vercel/og on my pages project, and I'm hitting "Your Functions script is over the 1 MiB size limit"
Nseemingly, the font is getting embedded not as a static file
Nbut
Nin the bundle
NI have two font weights, which sum up to be 600 KiB, so that's a big issue
Nactually thats not the issue, nvm
N│ __next-on-pages-dist__/functions/checkout/[id].func.js │ esm │ 1043.90 KiB │Nhow do I make this smaller...
NYou can't
Nyou buy the worker paid plan
Nah...
NThat's what I did
Bthat's very odd because you are indeed not supposed to use
<Html /> outside of pages/_document and both deployment methodologies use next build, so it's definitely weird that it works locally?
DWill
env.ASSETS be available in local (using getRequestContext()) and production when using next-on-pages?DI am not sure but I think you explicitly need to create a not-found page and export runtime constant to make it edge compatible.
JIt won't be available in local. I don't think there would be a simple way to make it work because the output directory doesn't exist yet with next dev
Ayes. that was the fix, pretty interesting
NCloudflare Docs
Deploy a full-stack Next.js site (recommended).
Ndocumented
Ni definitely recommend using C3 to init the projects, they have the good defaults already
GHey! Does anyone know if I can use the Next.JS middleware along with the fetch caching inside the CF workers? I want to cache a page based on some parameters that are not in the URL (like user country by ip, device type and language etc.). How can I do this with pages router and next-on-pages?
AOh, neat. I feel like I started using next-on-pages before this doc existed, i need to review/read it.
TI've been using Server Actions extensively in my project, had no issues yet. What do you mean by it doesn't play nice with the export const 'edge' ?
TI feel like they're blazing fast combined with d1
Njust dont put the edge export
Nit works
Ni think you need to put it in the page.tsx
Bdid u find a solution?
