FetchEvent constructor no longer accepts second argument

Problem

According to the FetchEvent spec the FetchEvent constructor accepts an optional second argument called init. I think this worked in 2.2.1 but stopped working in 3.0.0.

---

Motivation:

I’m using the init.request argument in my tests like so

new FetchEvent("fetch", {
  request: new CfRequest("/foo", { method: "GET" }),
})

to test the handler passed to addEventListener("fetch", (event) => {}) with a fake event. This creation of the fetchEvent now being marked as invalid by TypeScript.

[lookfirst]

It was complaining at first, but clearing the cache and restarting the project cleared that up. We have success! Thanks for your patience.

[vlovich]

I think this is a compliance issue in the runtime itself & not an issue with the types. We actually don’t support constructing a FetchEvent & the exposition of the constructor at all is an oversight in the typing. The next release will remove the FetchEvent constructor until it’s actually available in the Runtime.