workers-help
pages-help
general-help
durable-objects
workers-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
âš¡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd
web3
🤖turnstile
radar
web-research
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows-beta
Hi, I have a turborepo including a Next
the `persist` option of
persist
option of setupDevPlatform
doesn't appear to be working as expected, unless I have it configured incorrectly
```ts
if (process.env.NODE_ENV === "development") {
await setupDevPlatform({...Dynamic routes break my deployment
Hmmmmm the `getRequestContext` can't be
getRequestContext
can't be called within an actions.ts due to edge runtime requirement. Gana have to find another way to populate data to a client component.```
const { env, cf, ctx } = getRequestContext();
Warning: The function cannot be called in code from components using the Pages router.
const { env, cf, ctx } = getRequestContext();
Warning: The function cannot be called in code from components using the Pages router.
getServerSideProps
or middleware
)...Can we use `service` bindings with
service
bindings with getRequestContext()
?
I am trying to add it in wrangler.toml
but it is undefined
....nextjs deployments not working correctly
Hi @mr nooli @Fineshop Design, I've
this is what we've got 😓 : https://
getPlatformProxy
(and we do defer to that page in our docs)...Full-stack deployment · Cloudflare Pages...
Yes we implemented support for the fetch
server action without declaring `export const runtime = 'edge';`
using just `next dev` not that i know of
next dev
not that i know of but may be possible, im a huge donkey so hope im not leading you down the wrong direction, even now im wondering if i actually did create the KV in wrangler, or if it didn't just automatically do that,
you probably already saw this but the internal github doc:
```
https://github.com/cloudflare/next-on-pages/blob/main/internal-packages/next-dev/README.md...Anyone get D1 working with local
Honeycomb · Cloudflare Pages docs
That flag can only be set with Wrangler
Oh sorry yes, if you want to use pages:
Access to CF on Pages using Next.js
cf
object in the headers when using next.js on CF?
I'm trying to access botManagement
and it's not set on the request.cf, nor it it part of the headers....