[DOCS]: Provide an example of usage within Deno about webhooks.js HOT 4 CLOSED

Deno support is currently an issue for all Octokit modules.

We can try to fix some bugs and get some functionality working, but the proper solution will be when we rewrite all the modules as ESM native.

from webhooks.js.

Gotcha, I ended up making it somewhat work with:

import { createEventHandler } from "https://esm.sh/@octokit/[email protected]";
import { serve } from "https://deno.land/[email protected]/http/server.ts";

const secret = "mysecret";
const eventHandler = createEventHandler({ secret });
eventHandler.onAny(({ id, name, payload }) => {
  console.log(name, "event received");
});

serve(async (req: Request) => {
  if (req.url.endsWith("/webhooks")) {
    eventHandler.receive({
      id: req.headers.get("x-github-delivery"),
      name: req.headers.get("x-github-event"),
      payload: await req.json(),
    });
    return Response.json({
      message:
        "Triggered webhook",
    });
  } else {
    return Response.json({ status: "OK" });
  }
}, { port: 3000 });

from webhooks.js.

I know this issue has been closed, but currently createNodeMiddleware() cannot be used in Deno because the Deno core team don't want to support setTimeout() returning an object. Would you be amenable to a small patch that removed the use of setTimeout().unref() so that createNodeMiddleware() worked in Deno?

from webhooks.js.

Would you be amenable to a small patch that removed the use of setTimeout().unref() so that createNodeMiddleware() worked in Deno?

sure! I don't see a disadvantage. I hope I don't miss anything 😬

Longer term we want to move the create*Middleware into dedicated packages, as they introduce lots of dependencies and are often times not universal, like in this case.

from webhooks.js.