We're going to add compatibility date ASAP

Yeah, I just mean on the build machine itself.

(I want it too!)

It looks like Functions uses Wrangler when deploying (there's a log there that shows that, anyway).

Ah, yeah, we use wrangler to compile your folder of Functions into a Worker, but we manage that

It does the same thing that happens when you use

wrangler dev

locally 🙂

I'm running into an interesting problem w/ HTMLRewriter and middleware:

I have an

index.ts

and a

_middleware.ts

, and they both run HTMLRewriter in different ways. In wrangler, they both work fine, but when deployed to pages, the middleware one doesn't seem to work

it's definitely running, I can throw an error and it'll give 10XX, but otherwise the changes from

_middleware.ts

aren't getting reflected back in

index.ts

have there been any issues lately that might be related?

https://github.com/Mexican-Man/pages-csp-generator you can wrangler this w/ a

functions/index.ts

or `functions/_middleware.ts`:

ts
import { InjectCSPTags } from "../csp";

export const onRequest = [InjectCSPTags];

and an html page

I was only trying

_middleware.ts

deployed, but

_middleware.ts

and

index.ts

(w/ index.html obv) work identically locally

Hmmm.. this is certainly an interesting edge case. But in theory there should be nothing preventing you from chaining two HTMLRewriters together..

I unfortunately don't have a lot of time over the next few days, but @Greg Brimble | Cloudflare Pages might be interested in including this functionality into a Pages Plugin.. (which is to say that I would be very interested in having a CSP generator as a Pages Plugin 😄 ).. so he might have some time to take a look?

What's the support like for functions written in Go?

As in Go code that's compiled to JavaScript/WebAssembly?

Ok so you can't write Go code and deploy it as a Cloudflare function, it has to be compiled to JS or WASM?

I'm not sure if WASM is supported (it is in Workers) yet in Functions, but overall yes - JavaScript is required.

No WASM in Functions yet ☹️

I’ll try take a look at this today

ah I think I figured it out

half of it was me doing a bad job at handling

next()

, but HTMLRewriter just doesn't seem too happy when chaining requests sometimes

I resolved it by

await

-ing the first instance of HTMLRewriter, and that seemed to fix the issue

I don't have any concrete examples, I couldn't get anything to break/work consistently until now, so you can forget about it for now lol

I am wrestling with wrangler:) Does anyone know how I can connect to a KV data base when I run wrangler pages dev? On dash.cloudflare.com, the KV is called "TEST" with a "hello":"world" entry. Then in pages functions I have bound "TEST_DB" to "TEST". So that I in pages functions worker in production can call

env.TEST_DB.get("hello")

to get

"world"

and that works fine. But. How do I get to run and test this locally with

wrangler pages dev

? I have tried

npx wrangler pages dev . --kv TEST --binding TEST_DB=TEST

ps: I am running wrangler2 beta.

binding is for environmental variables, you should just use

--kv TEST_DB

nice, i try)

the wrangler pages KV is just a local copy of KV, and will not care about your bindings for production

maybe I am missing some pre-steps here. I get

null

instead for

"world"

.

I ran

npx wrangler pages dev . --kv TEST_DB