Hi, I want to statically export most of the pages in my website, but still be able to use server act
Hi, I want to statically export most of the pages in my website, but still be able to use server actions, can it be achieved?
H
AFrom what I can see in the docs, and my own experience, those env variables only get defined during build; also note that the url in the
CF_PAGES_URL var is the default .pages.dev one, if you plan on using a custom domain it's better to define your one env to specify itHI don't think so? Though you should be able to add it manually by putting it in a
.dev.vars
Aok, thanks; is it something that will be implemented at some point?
HHaven't heard anything about it. IIRC it is an issue from Next itself, not next-on-pages, as it expects to have control over routing, unless it is a fully static build
DIt only works with workers not next-on-pages (if I'm not wrong). Either use @vercel/og or @cf-wasm/og
Lyeah i switched back to the vercel one.
AThanks for the info, I'll override this flag
NDo durable object bindings work in
next dev
HThey should? Can you share your
wrangler.tomlThat looks fine? If you try logging the
envwell env.LOCK.idFromName and env.LOCK.get and the stub's fetch work
Nit just returns a 503 code
Nlet me actually log the response text
N[wrangler] Couldn't find
wrangler devI do have wrangler dev running for the worker tho
NDoes the worker's wrangler.toml need something specified too?
HYou have the DO bindings and the migrations defined?
NUhhh
NI dont have anything
HYeah, you need to tell it what DOs it exposes
Nis it just
NNin the worker
HYup, plus a migration that defines a "new_class"
HCloudflare Docs
Use a
wrangler.tomllets see now
Nadded these
Nsame error let me try restarting page dev
NSyntaxError: "undefined" is not valid JSON
at async Object.fetch (file:///home/neoney/code/sellhub/sellhub-checkout/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)
at async Object.fetch (file:///home/neoney/code/sellhub/sellhub-checkout/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)
Ntf?
Nlol
Nthats in page's logs
Nthats the response text*
HNi never do anything with json there tho...
HIIRC you can downgrade
wranglerbruh moment
Ndowngrade?
Nin worker or page?
Nworker
HBoth maybe? Tbh, I'm still not quite sure what the problem is, but there is an issue for it: https://github.com/cloudflare/workers-sdk/issues/5620
GitHub
Which Cloudflare product(s) does this pertain to? Wrangler core What version(s) of the tool(s) are you using? wrangler@3.50.0 What version of Node are you using? 20 What operating system and versio...
Ndang it always seems to return 204
Nah nvm im a moron
Nshould be simple fix
Nhell yeah
Ntime to wrap it in some helper function and have locks in critical code
JHi, I can't deploy dynamic pages using next-on-pages. Any idea why?
https://github.com/cloudflare/next-on-pages/issues/745
Trying to bump the issue as I'm behind the schedule and the deadlines are evil. Y'll understand
https://github.com/cloudflare/next-on-pages/issues/745
Trying to bump the issue as I'm behind the schedule and the deadlines are evil. Y'll understand
GitHub
next-on-pages environment related information Relevant Packages: @cloudflare/next-on-pages: 1.11.0 vercel: N/A next: 14.1.4 Description I'm currently building a website with Next.js 14 and Pris...
NWhen deploying a NextJs site to Cloudflare Pages, are the pre-rendered pages still served via the worker/function, or are they served statically without triggering the worker on each request?
