I am pretty sure this is the wrangler pages dev one. See that total cpu time

But what would it build if I already provided a _worker

This dies after I kill wangler but won't die after I kill my build watch one.

It looks like, whenever I overwrite _workers.js with

wrangler pages dev

running, the number becomes larger.

The command is just

npx wrangler pages dev ./dist

and nothing more.

And everything will be back to normal after I restart wrangler.

It is wrangler 2.16.0

(It is a bit cold after I killed wrangler 😦 )

What about as a producer? I see how you can use it as a producer in the Dashboard but not when using

wrangler pages dev

It seems like Service bindings are supported in prod, but not when running locally because https://github.com/cloudflare/workers-sdk/pull/2162 isn't merged. Is that right? How do people develop Functions with Service bindings in practice? Are there workarounds?

That's right, there's not any nice way of testing it locally at the moment

Hi! If anyone has a successful local setup for using D1 in Pages Functions, I'd love your help: https://community.cloudflare.com/t/working-with-d1-and-cloudflare-pages-in-local-development/501863

I'm having the same problem right now. https://blog.cloudflare.com/whats-new-with-d1/ tells us, that it's possible to download a d1 backup and use that locally. I just tried that and it works well. I run

wrangler pages dev ./public --d1=DB_BINDING --persist

This creates a

.wrangler/state/d1/DB_BINDING.sqlite3

file. I replaced that with the backup. I don't know if there's a shortcut somehow...

This is great—thank you! This part of the article is also very helpful: "Or you can simply use SQLite directly with the SQLite command line by running `sqlite3 .wrangler/state/d1/DB.sqlite3`". So basically the recommendation is to avoid things like

wrangler d1 execute <command>

and interface directly with the local SQLite file.

For what it's worth: apparently, even though not officially supported for Pages,

wrangler d1 execute --local <command>

will work if the binding is defined in wrangler.toml. So that is also kind of working for me. I'll update https://community.cloudflare.com/t/working-with-d1-and-cloudflare-pages-in-local-development/501863 with details!

I have a simple static pages with a form and a single simple function to save the form post data to the kv store. this requires me to have 1. astrobuild auto build on file changes (static site) 2. wrangler local backend I'm using the following command sine the docs are lacking i had to figure this out is this correct (works for me) wrangler pages dev --proxy=3000 --live-reload=true --persist=true --experimental-local=true --compatibility-date=2023-04-26

also now that its working how do use the command

npx wrangler kv:key list

with this local kv store?

--persist should be default why all this added complexity. I'm giving up on KV local dev (could not find a single updated doc) will try D1.

anyone ever had to parse a string of yaml (from a

Response

, not a file) to json in a worker / function?

https://www.npmjs.com/package/yaml should work fine: https://cloudflareworkers.com/#5bd33710458c37e6786b78f41283febe:https://tutorial.cloudflareworkers.com/

thanks, I'm not sure how to use that package inside a CFP function, I'm seeing (when I try to deploy to Pages) > ✘ [ERROR] 1 error(s) and 0 warning(s) when compiling Worker. > ✘ [ERROR] Could not resolve "yaml" am I missing something from your second link?

Did you install the package? Are you using Advanced Mode?

ah, I'm not, I'll take a look

will my _middleware in

/functions

still work if I switch out to using

_worker.js

?

No but you don't need to use advanced mode, that was just to see if you were bundling If you install the package, you should be good to go

thx @Walshy | Pages

So I'm trying to list all of the directory in the root of my R2 bucket. I followed along with a few different examples and I can't seem to get it to work. I did the binding as the documentation told me to.

export async function onRequest(context) {

    const options = {
        limit: 500,
        include: ['customMetadata'],
    };
    
    const obj = await context.env.NAME.list(options);
    if (obj === null) {
        return new Response('Not found', { status: 404 });
    }
    return new Response(obj.body);
}

This is my first time trying to do R2 through code so I could be something simple I'm missing.

body

is for

GET

you're listing so there is no bodies