Hey <@94508156243161088> thanks for getting back to me. I tested deploying a hello world next-on-pag

Hey @James thanks for getting back to me. I tested deploying a hello world next-on-pages project to see if the same issue occurred and it didn't! The caching works great. So it is definitely something wrong with my company's project setup. One thing I noticed is that we don't have a wrangler.toml -though it's unclear to me how we're deploying without it. Thanks again!

James•5/19/24, 8:39 PM

i see. that's interesting. you shouldnt need a wrangler.toml for fetch caching to work though...

lil.bigheadOP•5/19/24, 8:41 PM

O rly. I'll have a look and report back once they grant me access to the account, probably tomorrow

JJames are you using it only in server components? it'll be how nextjs builds your app ...

neoney•5/19/24, 8:53 PM

the issue was a bit different

neoney•5/19/24, 9:32 PM

well

neoney•5/19/24, 9:32 PM

the code for it was called

neoney•5/19/24, 9:32 PM

because

neoney•5/19/24, 9:32 PM

i was importing a package

neoney•5/19/24, 9:32 PM

that was importing it somewhere deep

neoney•5/19/24, 9:32 PM

i just refactored the pkg

neoney•5/19/24, 9:32 PM

so i only import the files i actually need

James•5/19/24, 10:33 PM

ah makes sense

Llaurent -> Just throwing it out there, my honest feedback on my cloudlare experience. I...

Baran•5/20/24, 1:57 PM

hi, how did you solve calling D1 binding? I get an error.

Short explanation including minimum code to reproduce the error: How can I access `env.DB` in my Pages/Worker on production?

ard•5/20/24, 3:06 PM

I am getting the error The script will never generate a responseThe script will never generate a response when trying to use fetch() in my generateMetaData function in NextJS 14. I've seen a lot of similar bugs reported on this but haven't been able to find a solution. Is anyone familiar with this?
I can reproduce this locally when running npx @Cloudflare/next-on-pages@1 and then using wrangler to do a preview, otherwise this works on local.
The error I was getting before reproducing on local (in my dev cloudflare url) was

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

A hanging Promise was canceled. This happens when the worker runtime is waiting for a Promise from JavaScript to resolve, but has detected that the Promise cannot possibly ever resolve because all code and events related to the Promise's I/O context have already finished.

SSM Did disabling "smart placement" fix the internal server error for you? I ask as ...

Nob•5/20/24, 8:16 PM

Hey, it seem like I have this problem again, after deploying it seem that the website load infinitely

Nob•5/20/24, 8:17 PM

maybe a cache problem because after some minutes after deployment the app works normally

Nob•5/20/24, 8:17 PM

or if I use a different browser it works

Hollo•5/21/24, 1:03 PM

can I somehow see the logs of a running deployment?

HHollo can I somehow see the logs of a running deployment?

Ian•5/21/24, 1:17 PM

You can tail them with Wrangler, or tail them in the web UI (Deployments > View Details (on your production deployment) > Functions > Begin Log Stream.

Ian•5/21/24, 1:17 PM

Note that in both cases you won't see prior logs, only things that happen after you start tailing.

Hollo•5/21/24, 1:18 PM

Thank you ill try that, since I have an issue that doesn't happen in the local preview and only on cloudflare.

Oosa I'm trying to get cache headers working for images loaded with custom loader whi...

thipperz•5/21/24, 8:03 PM

I'm facing this same issue: where should I put the _headers_headers file so I don't need to manually edit ./.vercel/output/static/_headers./.vercel/output/static/_headers after every build?

bun•5/22/24, 12:48 AM

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')

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

bun•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

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

just asking no need to be confrontive

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

bun•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 devnpx 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 devnext 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.

Hey <@94508156243161088> thanks for getting back to me. I tested deploying a hello world next-on-pag

Similar Threads

Similar Threads

Similar Threads