You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Discord.https** is a robust, modular library for implementing Discord HTTP interactions.
9
10
10
11
It handles various interactions and organizes them into modular routes, making your bot's code cleaner, easier to understand, and easier to maintain. It works seamlessly in both serverless and persistent server environments.
11
12
12
-
The core is production-ready and can be used in your new HTTP interaction bots.
> **Note**: Utility methods such as <interaction>.editReply() and <interaction>.deferReply() are currently in development, so you won’t need to manually handle the raw response object in the future.
58
44
59
-
> **Note(new)**: Utility methods were initially planned to closely follow Discord.js. However, since HTTP interactions are mostly used in a serverless environment, instead of having many layers of objects like Discord.js, an Eris-like approach will be adopted to keep the utilities minimal and lightweight.
45
+
> **Note**: Utility methods were initially planned to closely follow Discord.js. However, since HTTP interactions are mostly used in a serverless environment, instead of having many layers of objects like Discord.js, an Eris-like approach will be adopted to keep the utilities minimal and lightweight.
46
+
47
+
> **Breaking Update (latest note)**: The goal was to stay within the web-standard V8 engine, but `@discord/rest` heavily depends on the Node.js environment. There are two choices: either use `@discord/rest` or build a custom REST handler. For now, `@discord/rest` will be used. The focus is on the Edge network, primarily Cloudflare. However, Cloudflare recently added [native Node.js support](https://blog.cloudflare.com/nodejs-workers-2025/). Previously, Node.js support was polyfilled, which can be inefficient for servers due to extra overhead. Now, Node.js support is native. Hence, from now on, the focus will be on Node.js APIs instead of web-standard/browser-context APIs.
60
48
61
49
## Examples
62
50
51
+
>Examples are outdated. You are no longer required to handle the raw response. The core is still there, and you can use these examples as a reference.
52
+
53
+
Deprecate warning, this example can be serve as a basic idea, but it has been changed quite a lot since, with utility functions.
54
+
63
55
**You can view example/reference implementations here:**
-**Discord Interaction Docs:**[Responding to an Interaction](https://discord.com/developers/docs/interactions/receiving-and-responding#responding-to-an-interaction)
86
78
87
-
## Todo
79
+
## Todo for v4
88
80
89
-
-[ ] Build structures
90
81
-[ ] Build a simplified `npx create-app` command
91
82
-[ ] Implement tests
92
-
-[x] HTTP adapters to support all hosting environments. Currently implemented: Node.js adapter for [Node.js runtime](https://github.com/discord-http/nodejs-adapter) and [Cloudflare adapter for V8 isolates runtime](https://github.com/discord-http/cloudflare-adapter)
93
-
-[x] Examples
83
+
-[ ] Build channel, guild, etc wrapper
84
+
-[X]~~Build interaction wrapper~~
85
+
-[x]~~HTTP adapters to support most hosting environments~~. Currently implemented: Node.js adapter for [Node.js runtime](https://github.com/discord-http/nodejs-adapter) and [Cloudflare adapter for V8 isolates runtime](https://github.com/discord-http/cloudflare-adapter)
0 commit comments