Is it possible to use this API inside the cloudflare workers framework/engine?

[null-prophet]

I came across this amazing API and wondered if it was compatible with the cloudflare worker model.

I've seen an example from discord setting up a worker to respond as your bot and the basic ones work fine, was wondering how easy it would be to adapt this engine to the same.

https://discord.com/developers/docs/tutorials/hosting-on-cloudflare-workers

I was following this tutorial but the main issue is how the handle requests coming in:

export default {
  /**
   * Every request to a worker will start in the `fetch` method.
   * Verify the signature with the request, and dispatch to the router.
   * @param {*} request A Fetch Request object
   * @param {*} env A map of key/value pairs with env vars and secrets from the cloudflare env.
   * @returns
   */
  async fetch(request, env) {
    if (request.method === 'POST') {
      // Using the incoming headers, verify this request actually came from discord.
      const signature = request.headers.get('x-signature-ed25519');
      const timestamp = request.headers.get('x-signature-timestamp');
      console.log(signature, timestamp, env.DISCORD_PUBLIC_KEY);
      const body = await request.clone().arrayBuffer();
      const isValidRequest = verifyKey(
        body,
        signature,
        timestamp,
        env.DISCORD_PUBLIC_KEY
      );
      if (!isValidRequest) {
        console.error('Invalid Request');
        return new Response('Bad request signature.', { status: 401 });
      }
    }

    // Dispatch the request to the appropriate route
    return router.handle(request, env);
  },
};

and in their example they are using an itty-router instance to handle the requests.

The fetch method will get the requests in and if they are legit it passes to a handler and uses the discord-interactions code right now which is good but a bit verbose.

Any ideas would be appreciated, thank you.

[monbrey]

discord.js is designed for gateway connections, generally running as a Node application. It's not intended to be used for http interactions.

However, the discord.js library is composed of several packages that can be used independently - you may be interested in @discordjs/rest for making API calls and @discordjs/builders for building components, embeds etc in responses.

There's also a standalone structures package being built for class structures to represent Discord objects (User, Message etc)

[null-prophet]

Thankyou @monbrey I had a go with the command registration part and that was working nicely.

the code I have written is a bit more verbose (with case statements for handling specific response types etc) but its working.

I started with TS but initially I had a bunch of problems with namespaces etc, mostly in the cloudflare land and putting in some of the feautres I was using from a tutorial. Got it working now with simple JS. If thats stable then great. I'll definitely look at using these APIs in the future. Thank you so much for the reply.

[Crypt0Beaver]

Hi,
And for gateway type applications, would Discord.js work on cloudflare workers? They seem compatible with node.js, however when trying juste to import discord.js and starting wrangler there are a bunch of reference errors.

[NickantX]

Hi, And for gateway type applications, would Discord.js work on cloudflare workers? They seem compatible with node.js, however when trying juste to import discord.js and starting wrangler there are a bunch of reference errors.

Cloudflare Workers don't support running a long-lived process, which is exactly what a gateway type application needs to do. The application stays connected to Discord via their websocket gateway and receives events that way. Cloudflare Workers are better suited for modern apps using HTTP Interactions, where Discord sends an HTTP request when an application command is invoked. This does not require a gateway connection, and is a popular way to easily build a scalable Discord app. But discord.js is not designed for these types of applications.

[sayyidyofa]

So why does there a "Powered by Workers" badge in the readme

I wasted my time trying to make it work... I'll just use raw api calls then

[didinele]

So why does there a "Powered by Workers" badge in the readme

Because we have an OSS partnership with them, like we do with Vercel.

That being said, you could use @discordjs/core/http-only in workers for a higher level of abstraction. See https://discordjs.dev/docs/packages/core/1.0.1