export const ```runtime = "edge";``` do i have to put this in every page.tsx / route.ts / layout.ts
export const
do i have to put this in every page.tsx / route.ts / layout.tsx ?
do i have to put this in every page.tsx / route.ts / layout.tsx ?
Nevery page.tsx / route.ts that are not static (that use headers, cookies etc)
Nbut you don't need for your server action
LVercel image optimization, log drains for log retention, sentry integration
BI have a Nextjs v14 app on my local machine. I added
When I build and deploy the app using wrangler on my local machine, it picks up the flag and I don't get any node js compatability errors; but the cloud instance didn't pick it up (see attached image). I can manually add this flag using the Cloudflare dashboard, but I would prefer to automate the process in
FIXED: I had to add
wrangler.tomlWhen I build and deploy the app using wrangler on my local machine, it picks up the flag and I don't get any node js compatability errors; but the cloud instance didn't pick it up (see attached image). I can manually add this flag using the Cloudflare dashboard, but I would prefer to automate the process in
wrangler.tomlFIXED: I had to add
compatibility_date = "2024-05-13" to wrangler.toml
Jthe only reason it's shelved is because we dont have tests for testing the fetch cache works properly which would validate that this doesn't interfere with it, and i haven't had time to write any yet or test this myself since i basically married my job
Jnot sure regarding react
SHi, I'm working on a project that uses the pages router but it fails on the Cloudflare Pages build.
I export
I export
runtime = 'experimental-edge on my custom _app but not on the page.tsx itself because I run into missing packages that's related to Firebase Auth. Exporting runtime = 'edge' also doesn't work. Everything works as intended on local development but it breaks on build. Is there anything else I should try?
MMake sure that page.tsx for /posts/[slug] has the export const runtime = ‘edge’
Nadded some asynclocalstorage stuff to my nextjs app, and it gets bundled into the frontend code???
LHey folks, I'm having issues caching fetch requests within Server Components when we deploy to CF Pages. The Next docs mention time-based revalidation, e. g.
This works as expected in dev - the server will only re-fetch 60 seconds after the last fetch occurred. Once we deploy though, each request to the page makes a fetch every time.
Is this where the KV bindings come into play? I don't believe my team set that up.
const users = await fetch(USERS_URL, { next: { revalidate: 60 } }).then(…)This works as expected in dev - the server will only re-fetch 60 seconds after the last fetch occurred. Once we deploy though, each request to the page makes a fetch every time.
Is this where the KV bindings come into play? I don't believe my team set that up.
Rhi team, for better reach reposting an open question here Worker using multiple modules in a single bundle
Basically seeing warnings as ✘ [ERROR] workerd/jsg/_virtual_includes/jsg/workerd/jsg/modules.h:443: warning: NOSENTRY Worker using multiple modules in a single bundle.
Basically seeing warnings as ✘ [ERROR] workerd/jsg/_virtual_includes/jsg/workerd/jsg/modules.h:443: warning: NOSENTRY Worker using multiple modules in a single bundle.
Jcan you open an issue on the next-on-pages github repo please
Jare you using it only in server components? it'll be how nextjs builds your app so im not sure we can do anything about that
LHey @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!
Ji see. that's interesting. you shouldnt need a wrangler.toml for fetch caching to work though...
LO rly. I'll have a look and report back once they grant me access to the account, probably tomorrow
Nthe issue was a bit different
Nwell
Nthe code for it was called
Nbecause
Ni was importing a package
Nthat was importing it somewhere deep
Ni just refactored the pkg
Nso i only import the files i actually need
Jah makes sense
Bhi, 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?
Short explanation including minimum code to reproduce the error: How can I access `env.DB` in my Pages/Worker on production?
AI am getting the error
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
The 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.
NHey, it seem like I have this problem again, after deploying it seem that the website load infinitely
Nmaybe a cache problem because after some minutes after deployment the app works normally
Nor if I use a different browser it works
Hcan I somehow see the logs of a running deployment?
IYou can tail them with Wrangler, or tail them in the web UI (Deployments > View Details (on your production deployment) > Functions > Begin Log Stream.
INote that in both cases you won't see prior logs, only things that happen after you start tailing.
HThank you ill try that, since I have an issue that doesn't happen in the local preview and only on cloudflare.
TI'm facing this same issue: where should I put the
_headers./.vercel/output/static/_headers
Bi'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:
whenever im refreshing like multiple times repeatedly, somewere between 5th or 10th refresh results in a 500 internal server error and the logs say:
BAlthough the main page that's displayed is a server component, some child compnoents might be client, but thats about it
Bwhy you use 14.1 ?
GWhen using zero-trust and next-on-pages I don't see the CF_Authorization cookie is this expected?
Gn/m it's in the header but it's not being parsed
Bjust asking no need to be confrontive
Bbut try 14.2.3, it seems to be working
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.
