workers-and-pages-help
pages-help
general-help
durable-objects
workers-and-pages-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-runtime
🤖turnstile
radar
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
pipelines-beta
containers-beta
I also have another issue with next-on-
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

Actually if I can add a scheduled
hey folks- having trouble deploying my

Hi @mr nooli @Fineshop Design, I've
Hey folks - trying to migrate from the
setupDevBindings to the new setupDevPlatform - I've got it working except it seems to not be pointing at the correct local sqlite DB for the D1 driver.
This was my previous config file, have I not specified the wrangler toml correctly?
```ts...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...