IThat was not a rude question at all; they were legitimately asking why you needed a particular version. That stuff matters when troubleshooting. Please don't bring a hostile attitude like that in here and expect help.
IThis is often an issue with server components + suspense I think. Make sure you really follow the rules of how you can use server components within client components (can only be passed as children) and mark client components actually as client components, even though the parent is a client component.
Bi have that issue on a server component page that isnt even async, but has some client components beneath
IFor people having issues with "The script will never generate a response", I ran into this too with Next.js + Storyblok & Server Components. After following the rabbit hole of the source code of Storyblok I noticed that it stores the client in a globally scoped variable. I had a suspicion that that might have something to do with it, since it might re-use these in subsequent requests, which workers doesn't like? I forced the re-initalization of the Storyblok client on every request we do to it, which seems to have solved the problem for us.
HHello, I am still struggling to understand on how to run a next-on-pages dev environment.
How do I run it like
If I run
If I run
How do I run it like
npx next devIf I run
wrangler pages devIf I run
wrangler dev
Mhas anyone had a chance to try next15? curious how it goes, going to give it a shot a lil later hopefully
Jthank you for this!
RI have a weird build error. I have the .node-version, .tool-versions and mise.yaml config files to tell the builder to build using 20.5.1. I see asdf installing 20.5.1 correctly, but then during the build it all of a sudden says it found 18.17 to build with. My site will not build with 18.x so I can no longer use the cloudflare builder. It works fine building it locally and uploading it using wrangler pages deploy and the function works correctly (ie. SSR using nexjs with a next-on-pages vercel build.)
RIt will also work using github actions, of course, but then it's the role problem I mentioned in the other channel making this really suboptimal for large enterprises.
Bdevelop with
By default, the entry point is the build directory, so add the following to your
Note:
next devwrangler pages devBy default, the entry point is the build directory, so add the following to your
wrangler.tomlNote:
wrangler devpageswrangler devwrangler pages dev
HThank you for clearing that up!
NHi, there is a problem with fetch request with "force-cache" that are loading forever randomly when its a file bigger than 1Mb in server components
Nin prod and in dev
RHas anyone used next-on-pages with the analytics-engine in development? For me the env binding stay undefined.
I
DHi, can any one help me out from the Worker error 1101, this error occurs when i use the optional catch-all segments from dynamic routes. wrangler dev log returns -- TypeError
Invalid URL string.
Invalid URL string.
DHi i have used addEventListener in my index pages, still i receive the same worker error 1101. i am sure were to handle the addeventlistener.
ZHi! I have built a NextJS app fully on Edge and so far it went good. Suddenly I've crossed the bundle size limit
Generated Pages Functions bundle size (49446697) is over the limit of 25.0 MiB
NDoes anybody know how to prepare for next 15 fetch changes which don't cache by default anymore?
See https://nextjs.org/blog/next-15-rc#caching-updates
If I try to restore/prepare the old behavior with
See https://nextjs.org/blog/next-15-rc#caching-updates
If I try to restore/prepare the old behavior with
fetch('myUrl', { cache: 'force-cache' })GitHub
Which Cloudflare product(s) does this pertain to? Workers for Platforms What version of Wrangler are you using? Latest What operating system are you using? All Describe the Bug Making a fetch reque...
The Next.js 15 Release Candidate (RC) is now available. This early version allows you to test the latest features before the upcoming stable release.
Nhm maybe i should check if it works if i follow https://github.com/cloudflare/next-on-pages/blob/main/packages/next-on-pages/docs/caching.md
Nshould this maybe be a linting rule that one could contribute? Feels like a foot gun as it's only happening at runtime on pages/workerd and not during build or local development with
next dev
SAm I correct in understanding that getRequestContext only works in the App router? And in order to access the bindings in the wrangler.toml file for Pages router, I have to use process.env instead? Any help would be appreciated
CHow can we debug a next js app running
I have a next js app that works perfectly when on node / nextjs, but when I try testing it using
If I could set break points to debug the app, it would help me figure this out.
wrangler pages devI have a next js app that works perfectly when on node / nextjs, but when I try testing it using
wrangler pages dev[wrangler:err] TypeError: This ReadableStream is disturbed (has already been read from), and cannot be used as a body.
If I could set break points to debug the app, it would help me figure this out.
CI tried setting a dev port using
And now see an error occationally
And now see an error occationally
Unused stream created
CWhile I was unable to debug using breakpoints I figured out why I was facing
And I don't think cf pages support debugging using breakpoints yet
This ReadableStream is disturbed (has already been read from)And I don't think cf pages support debugging using breakpoints yet
Lis there an ETA to when 
routewranger.tomlYes, kinda annoying workers and pages are separate
TWhat is the difference between deploying with
wrangler pages deploy
R@all
Build Failed: build exceeded memory limit and was terminated. (Preview and Prod)
I tried the same by increasing --max-old-space-size=8192 but deployment continued to have the same error as stated.
|14:08:46.399|Success: Finished cloning repository files|
|14:18:58.679|Failed: build exceeded memory limit and was terminated|
Deployment id: 9aff3dcd-9f38-4002-93db-5020409e5a8b
node: 18.17
Would appreciate any help.
Build Failed: build exceeded memory limit and was terminated. (Preview and Prod)
I tried the same by increasing --max-old-space-size=8192 but deployment continued to have the same error as stated.
|14:08:46.399|Success: Finished cloning repository files|
|14:18:58.679|Failed: build exceeded memory limit and was terminated|
Deployment id: 9aff3dcd-9f38-4002-93db-5020409e5a8b
node: 18.17
Would appreciate any help.
CI am trying to set a response header in the middleware and read it in pages or layout routes. But this isn't working.
I have filed a bug report here - #797
Quick summary in the thread
I have filed a bug report here - #797
Quick summary in the thread
GitHub
next-on-pages environment related information System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020 CPU...
THi, how do I run
next devnext devruntime = "edge"
AGitHub
Verify canary release I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: win32 Arch: x64 Version: Windows 10 Pro Binar...
II just created a new next project with cloudflare cli and added the 
runtime='edge'
TI'm on a Mac
TBut just to confirm it's supposed to not break next dev? As in I don't need to switch to Wrangler or something like that
TI think the issue is something else; it's the env vars
Thow am I supposed to manage environment variables in
next devNEXT_PUBLIC_Maybe this can help you, it's recommended to use
getRequestContext.dev.varsCloudflare Docs
Deploy a full-stack Next.js site (recommended).
Tdoes this work also outside of route handlers?
T(i.e. I can replace
process.envgetRequestContext()i think it works locally in dev mode but not in a build
Ias long as you are not using it at the top level, it works anywhere rsc, route handlers, server actions
Ttop level being?
Twould it work somewhere like
next.config.jsno
TI need it to work there so I guess that's a no go
LHow many worker invocation are counted when accessing bindings in next-on-page?
For example, if i visit simple hello world page
that would be 1 invocation
if i visit another page which fetches a row from d1(connected via binding) is that 1 + 1 invocation or a single invocation?
For example, if i visit simple hello world page
that would be 1 invocation
if i visit another page which fetches a row from d1(connected via binding) is that 1 + 1 invocation or a single invocation?
