#Cloudflare Pages bindings in a Qwik City loader

7 messages · Page 1 of 1 (latest)

split solstice
#

so I've added Cloudflare Pages integration using npm run qwik add and all the files appear to be there.

now what? How do I access the bindings locally?

I've updated the "serve": "wrangler pages dev ./dist --kv KV" script, do I have to start in parallel with the "start": "vite --open --mode ssr" script?

do I have to declare the mocked bindings somewhere else?

split solstice
#

in the https://developers.cloudflare.com/pages/framework-guides/deploy-a-qwik-site/ docs it is stated:

Note that as part of the cloudflare-pages adaptor installation, a functions/[[path]].ts file will be created.

I just reran npm run qwik add cloudflare-pages and functions directory was not created, so I assume the docs are outdated already?

Deploy a Qwik site · Cloudflare Pages docs

Qwik is an open-source, DOM-centric, resumable web application framework designed for best possible time to interactive by focusing on resumability, …

split solstice
#

alright, so seems like I got it working, well kind of:

  1. Read the binding in the loader like this: export const useDadJoke = routeLoader$(async ({ platform: { env: { KV }}}) => {
  2. npm run build (defined as "build": "qwik build")
  3. npm run serve (defined as "serve": "wrangler pages dev ./dist --kv KV")

now I have to figure out how to streamline this and make the build command listen to changes and the both build and run can be ran in parallel

split solstice
#

figured that out:

 "build.server": "vite build -c adapters/cloudflare-pages/vite.config.ts",
 "build.server.watch": "npm run build.server -- --watch",

so npm run build.server.watch and once this is up and running and listening to the changes, you can fire "serve": "wrangler pages dev ./dist --kv KV" (that is npm run serve) and it works

shrewd socket
stiff stag
#

I'd like to know as well.

shrewd socket
#

I eventually gave up on this and created a monorepo solution instead. So a CF Pages project, and a CF Worker in the same monorepo. They 2 apps can share types and the CF pages app can access KV, D1 data etc through http calls to the CF worker. No restarts needed for code changes so the DX is good.