Eris
DIAdiscord.js - Imagine an app
•Created by #ToiYeuSweetLiquor <3 on 4/22/2025 in #djs-questions
Deno or Bun support ?
This is with an active any message listener, by the way
13 replies
DIAdiscord.js - Imagine an app
•Created by #ToiYeuSweetLiquor <3 on 4/22/2025 in #djs-questions
Deno or Bun support ?
13 replies
DIAdiscord.js - Imagine an app
•Created by #ToiYeuSweetLiquor <3 on 4/22/2025 in #djs-questions
Deno or Bun support ?
My one-server bot barely goes above 0.10% CPU usage and I would assume that if I scaled it, it would stay about the same.
Generally, just be performant in the rest of your code, and use workers where you can to multithread.
13 replies
DIAdiscord.js - Imagine an app
•Created by #ToiYeuSweetLiquor <3 on 4/22/2025 in #djs-questions
Deno or Bun support ?
13 replies
DIAdiscord.js - Imagine an app
•Created by #ToiYeuSweetLiquor <3 on 4/22/2025 in #djs-questions
Deno or Bun support ?
Deno supports d.js pretty well, my bots pretty much all run on Deno and I don't see any issues
13 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
'Twas merged and works well!
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
so it's fixed™️ now?
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
imo I dont mind the spam, it's nice to see to know my project is still running
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
yeah, there's just a minor console spam issue since Deno didn't implement a certain Websocket function yet, but there's a fallback it uses instead so it still works just fine
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
alright, awesome! I'll keep an eye on @discordjs/ws and once the patch is in I'll just make my project use dev somehow. thanks for keeping us informed!
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
from what I see:
- Deno is following web specifications which @discordjs/ws doesn't implement right
- Node uses something nonstandard (?) [the
ws module] that doesn't include the protocol value, which is what causes the issues here
- Bun is idk39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
bun has no API documentation whatsoever so we will ignore it
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
node, by the looks of it, uses the
ws module which... well, doesn't do that39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
const connection = new WebSocketConstructor(url, {
handshakeTimeout: this.strategy.options.handshakeTimeout ?? void 0
});
deno recently made a change (?) that made arg #2 the protocol, in line with web standards. arg #3 should be ops now
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
OK now I know half what I'm doing here
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
wait, all old versions had void 0, nevermind dead end
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
wait no
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
this was previously
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
FOUND IT
39 replies
DIAdiscord.js - Imagine an app
•Created by DarkstarDraconis on 5/7/2024 in #djs-questions
Deno / Websocket error
ok no it doesn't pin to 1.0.2, likely a ws update broke it
39 replies