worker-rs is all hand-written bindings to the Workers APIs using wasm-bindgen and web-sys crates for the most part

You’d have to write your own “glue” between C# and JS

Time for my weekly question up : did anyone manage to use middleware on an angular CSR project yet ? my 14days old ticket still has no answer.

Thank you for the information. I will have to do some research on how to do that. I haven't every done anything like that before.

Never used Angular but doesn't the regular

functions/_middleware.js

work?

It works only in wrangler basicly

if it works in wrangler, it should work in prod

Exactly 😄

can you share more details?

Sure

It starts here

what's your pages.dev?

sent over DMs

I try since days to get my head arround it and googled so much ..... how can I have a html form on a static page with cloudflare pages and send an email to me with the form submission via cloudflare pages function? Have a look here: https://gist.github.com/michael-voit/6295d286331ff6049d0bd8b60d64a4ff I have a form in the html document (form.html), a form.js to prevent the default form submission behavior and instead "give it" to a cloudflare pages function sitting in a file contact.js in folder /functions/api I was able to test and iterate it to the point, that the first two steps are working - but it seems that contact.js is not transformed into a function - or something like that. Anybody has done that before? Or anyone time to look over it? THANKS SO MUCH IN ADVANCE!

Is there an equivalent of @Cloudflare/workers-types for functions written in Typescript. I would like to type context in onRequest( context ). I don't think the ExecutionContext from workers-types is right for functions.

yup, I think you should export a variable (or function) with type

PagesFunction

that gets one argument that receives an

EventContext

, which contains the

ExecutionContext

ok so to verify: the context in onRequest( context ) has type EventContext?

correct - if you export it as

export const onRequest: PagesFunction = (context) => { ... }

, it pickes up argument and return types automatically

(edited, I'm tired)

Thanks much. That one worked like a charm 🙂

Following docs here (https://developers.cloudflare.com/pages/platform/functions/advanced-mode/#set-up-a-function), using example code. Getting deployment error

Transforming async functions to the configured target environment ("es5") is not supported yet

Trying to fix the routing for two SPAs hosted under the same pages project

Route

/*

maps to SPA 1 but I want to map

/spa2/*

to SPA 2

That looks like something is trying to bundle the _worker.js file, which it shouldn’t be doing. Where do you have it?

It might be the routes.json file

_worker.js should be in the output directory, not in the

functions

folder

thanks, so it should be copied into

/dist

during the build step?

Yes

Hi sorry if I'm blind but looking for a needle in the haystack it looks like this feature is under active development and I do like the direction it is going. My question is there a cheat seat or where is the code that calls our pages functions? Do you know how it works when we export an

onRequest

method. I noticed you use

onRequestPost

do all https request methods work like this Can I export onRequestGet, onRequestPost, and onRequest all in the same route. Would onRequest get everything or would the more specific one win. Is there a place where everything available from cloudflair in pages functions is documented For example waitUntil kv d1 etc. I noticed here I need a list of modules to import and their interfaces. or available functions that can be exported. If there is a spec doc for the routing naming that might be nice. Or something if anyone has that in a project somewhere 🙂 Let me know what you have found