Not sure 😄

That indicates a return type

Yeah but what you have now indicates input params

Not sure how to type the whole thing tbh 🤷‍♂️

Oh wait.

It's a const, right?

Can you type the const?

so export const onRequestGet: PagesFunction = ...

Oh that's it! Perfect thanks

Great 🙂

Now just to work out how to type this haha

Whew...

😅

No clue, sorry 😆

I'll work it out, thanks anyways

declare global {
  const clientID: string
}

should work

Not for when you're using functions, that comes under env.clientID, not the global clientID variable

Then wrap clientID in

env {}

for that type--I am not familiar with Pages but have to do this in Workers TS projects.

If it is mimicking node's

process.env

then you must

declare global {
  namespace NodeJS {
    interface ProcessEnv {
      clientID: string
    }
  }
}

It's not node's env but that snippet might let me work out how to solve it

Ended up creating my own type which does the trick. Thanks all

Hello everyone! Playing around with pages and functions... sorry if this is a noob question, but please point me in the right direction. How can I work with functions locally? Does wrangler work for this? What command? I tried wrangler dev script, but i get an

Unexpected token 'export'

error. Please and thank you in advance!

hmmm, weird, I tried that earlier and it didn't work, but now its working!

Thanks!

Hi guys, Middleware: passing a URL to the next function works locally, but not after deployment. I am trying to rewrite URLs based on country and device (using functions, I want to mimic the page transform rule rewrite) Why do we have an option to pass a new url to the next function if it ignores and we get the original response? @Walshy | Pages

You would type it like this:

export type APIEnv = {
    ADMIN_KEY: string;
    DEV: string;
    KV_LAUNCHING: KVNamespace;
}

type Params = "key" | "fname" | "lname";

export type MiddlewareData = {
    logs?: string[];
};

export const onRequestGet: PagesFunction<
    APIEnv,
    Params,
    MiddlewareData
> = async ({ env, params, request, data }) => {
  ...
}

The APIEnv, Params, MiddlewareData can be named anything you like of course.

that's so useful! Thanks so much <3

would love for that to be documented

I have an idea of making use of functions, but I'm not sure whether it is possible to implement. I have a webpage deployed on Cloudflare Pages. In it, there is a HTML Form. My idea is to create a function to handle the form submission (POST request) and then send an email to my personal mail box (or the one under my Cloudflare domain) for every new form submission. I believe the first part is easy but I'm not sure about the send email part. Is it possible? Please tag me on this