i've been encountering some weird issue, has anyone else had anything similar? whenever im refreshi

i've been encountering some weird issue, has anyone else had anything similar?

whenever im refreshing like multiple times repeatedly, somewere between 5th or 10th refresh results in a 500 internal server error and the logs say:

  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'default')

  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'default')

  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'default')

  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error) TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'useContext')
  (error)  ⨯ TypeError: Cannot read properties of null (reading 'default')

bunOP•5/22/24, 12:50 AM

Although the main page that's displayed is a server component, some child compnoents might be client, but thats about it

Mmartior Has anyone else seen that _worker.js balooned in size after upgrading to next 14...

bunOP•5/22/24, 1:36 PM

why you use 14.1 ?

Gabe•5/22/24, 6:30 PM

When using zero-trust and next-on-pages I don't see the CF_Authorization cookie is this expected?

Gabe•5/22/24, 6:36 PM

n/m it's in the header but it's not being parsed

bunOP•5/23/24, 8:44 AM

just asking no need to be confrontive

bunOP•5/23/24, 8:44 AM

but try 14.2.3, it seems to be working

Mmartior yes it was, it was a rude question

Ian•5/23/24, 9:27 AM

That 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.

Bbun i've been encountering some weird issue, has anyone else had anything similar? ...

ItsWendell•5/23/24, 12:46 PM

This 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.

bunOP•5/23/24, 12:47 PM

i have that issue on a server component page that isnt even async, but has some client components beneath

ItsWendell•5/23/24, 12:52 PM

For 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.

Hollo•5/24/24, 5:06 PM

Hello, I am still struggling to understand on how to run a next-on-pages dev environment.
How do I run it like

npx next dev

npx next dev

would (with instant updates as I change the code, instead of needing to compile everything all the time).
If I run

wrangler pages dev

wrangler pages dev

it will run an outdated version of what I locally have (which I assume is my last build).
If I run

wrangler dev

wrangler dev

it is asking me to specify an entry point, which I don't now what to put in there for the dev environment.

Matt•5/24/24, 7:42 PM

has anyone had a chance to try next15? curious how it goes, going to give it a shot a lil later hopefully

Bbun but try 14.2.3, it seems to be working

jg•5/24/24, 8:45 PM

thank you for this!

richtera•5/24/24, 10:01 PM

I 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.)

richtera•5/24/24, 10:02 PM

It 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.

HHollo Hello, I am still struggling to understand on how to run a next-on-pages dev env...

Baran•5/25/24, 7:19 AM

develop with

next dev

next dev

. When you are done developing and want to deploy, run

wrangler pages dev

wrangler pages dev

to test the final version before deployment.

By default, the entry point is the build directory, so add the following to your

wrangler.toml

wrangler.toml

pages_build_output_dir = ".vercel/output/static"

pages_build_output_dir = ".vercel/output/static"

Note:

wrangler dev

wrangler dev

runs a worker, but next-on-pages is a

pages

pages

feature (which is a subset of workers). So,

wrangler dev

wrangler dev

will probably not be compatible with next-on-pages, so please use

wrangler pages dev

wrangler pages dev

BBaran develop with `next dev`. When you are done developing and want to deploy, run `w...

Hollo•5/25/24, 10:39 AM

Thank you for clearing that up!

Nob•5/27/24, 7:43 PM

Hi, 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

Nob•5/27/24, 7:43 PM

in prod and in dev

Rodrigo•5/28/24, 9:33 PM

Has anyone used next-on-pages with the analytics-engine in development? For me the env binding stay undefined.

Isaac McFadyen•5/28/24, 9:43 PM

^ solved in analytics-engine

in the future please don't cross-post across channels.

dhanasekar•5/29/24, 1:59 AM

Hi, 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.

dhanasekar•5/29/24, 2:02 AM

Hi i have used addEventListener in my index pages, still i receive the same worker error 1101. i am sure were to handle the addeventlistener.

zbeyens•5/29/24, 10:17 AM

Hi! 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

Generated Pages Functions bundle size (49446697) is over the limit of 25.0 MiB

with empty pages going over 3MB. I'm blocked on this, is there a way to measure / debug / split parts to find the dependency cause? Note that Vercel deploys it successfully without crossing their limit. I'd love to stay on Edge/CF

youflix.7ed3f186-8065-4e32-abbe-d6f61f13db19.log110.65KB

num•5/30/24, 8:51 AM

Does 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

fetch('myUrl', { cache: 'force-cache' })

fetch('myUrl', { cache: 'force-cache' })

the worker throws an error due to https://github.com/cloudflare/workerd/issues/698 .

GitHub

🐛 BUG: The cache field on RequestInitializerDict is not implemented...

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...

Next.js 15 RC

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.

num•5/30/24, 8:52 AM

hm 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

num•5/30/24, 9:30 AM

should 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

next dev

Sej•5/30/24, 9:59 AM

Am 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

cj•5/30/24, 4:40 PM

How can we debug a next js app running

wrangler pages dev

wrangler pages dev

I have a next js app that works perfectly when on node / nextjs, but when I try testing it using

wrangler pages dev

wrangler pages dev

I get the following error

[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.

cj•5/30/24, 5:00 PM

I tried setting a dev port using

wrangler pages dev --inspector-port 9229

wrangler pages dev --inspector-port 9229

And now see an error occationally

Unused stream created

cj•5/31/24, 8:07 AM

While I was unable to debug using breakpoints I figured out why I was facing

This ReadableStream is disturbed (has already been read from)

This ReadableStream is disturbed (has already been read from)

.

And I don't think cf pages support debugging using breakpoints yet

luna•6/1/24, 8:46 AM

is there an ETA to when

route

route

will work for pages in the

wranger.toml

wranger.toml

? kinda annoying that workers and pages are still seperate..

cj•6/1/24, 10:03 AM

Yes, kinda annoying workers and pages are separate

thipperz•6/2/24, 11:50 PM

What is the difference between deploying with

wrangler pages deploy

wrangler pages deploy

or by pushing a commit to preview branch? Specifically for VARS and stuff, my NEXT_PUBLIC_APP_URL is only working when git pushed

Rishabh•6/3/24, 10:54 AM

@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.

Flare•6/3/24, 10:57 AM

Please do not post your question in multiple channels per the rules at No Access. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.

cj•6/3/24, 5:33 PM

I 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

GitHub

[🐛 Bug]: Failed to read header in page / layout after setting it in...

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...

t4•6/4/24, 4:31 AM

Hi, how do I run

next dev

next dev

with edge runtime? When I load up my app on

next dev

next dev

with

runtime = "edge"

runtime = "edge"

it shows a blank screen

Tt4 Hi, how do I run `next dev` with edge runtime? When I load up my app on `next de...

aspecs•6/4/24, 4:40 AM

https://github.com/vercel/next.js/issues/53562

GitHub

error TypeError: Cannot read properties of undefined (reading '') w...

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...