You doing a post request right ?

ahh Post

Dang it

:/

So sorry

:)

Done it myself

Many times

One more question! Where do I see the request body?

you have to

await request.text()

i think?

something like that

Correct

Hmm! Just like worker APIs right?

hmm, let me try

Yes

Thank you for creating this. It isn't abundantly clear through docs that KV has a local store independent of production store (the one you can edit via dash.cloudflare.com). That confused me until I tried deploying and suddenly, data!

Unrelated: When I run Next.js

next dev

I can't call functions after running

wrangler pages dev

proxied to the same port. Same result with

wrangler pages dev -- next dev

. Seems like Next assumes anything unmatched under root is a 404, preventing wrangler's dev server from accepting functions. I'm just using a different port, which isn't the end of the world, but was wondering if anyone deploying Next to Pages has encountered this & there's a way to tell Next to ignore my function paths.

This part in the document Should be

export async function onRequestPost({request}) {

?

No problem it stumped a lot of people including myself

Hey, am I correct in saying that pages functions only supports js for the moment? If so are there plans to support WASM as well?

I've noticed the same and am also wondering who I have to bribe to get WASM support sooner than later?

Tried to figure it out, making KV persist locally using miniflare, right? Is it currently supported with pages-functions?

Not yet, I don't think, though they are working on it.

Anyone have a good example of using strong typing for a PagesFunction? For example,

export const onRequestGet: PagesFunction = async ({ env, params }) => {
  // Can't find a way to type the params because PagesFunction says it should be a string.
  const id = params?.id;

  const aws = new AwsClient({
    // `env` is "unknown" and I can't modify it with any typing on line 1
    accessKeyId: env.B2_ACCESS_KEY_ID,
    secretAccessKey: env.B2_SECRET_ACCESS_KEY,
    region: "...",
    })
}

PagesFunction

takes a three generics: the env, params, and data.

Right, but I'm just not understanding how to do that.

Are you saying you want to give

{env, params}

a type or am I missing something else?

has anyone had any luck getting environment variables to load via wrangler?

just looking at the

--help

I don't even see the

--env

option for

page dev

Should be

—binding