Encountering Error `TypeError: emitter.getMaxListeners is not a function`
Happens as soon as I run the code. I am using ts-node so I have no idea if this is the reason why.
Solution:Jump to solution
I mean, using
ts-node
is like a minefield, it doesn't always behave as desired and most of the time it's more efficient to use tsc --watch
+ node .
😅8 Replies
Can you share the code, please?
Or at very least, the listener's options
Are you overriding
container.client
somewhere?no
the error seems to occur when I am using the compiled pieces
and not the ts versions
Solution
I mean, using
ts-node
is like a minefield, it doesn't always behave as desired and most of the time it's more efficient to use tsc --watch
+ node .
😅Gotcha, I mean I changed where the pieces are loaded to src and it works for now
so ima just put that off as a ts-node bug
TL;DR: Do not use
ts-node
, use tsc-watch
instead.
We very strongly discourage using ts-node
because it was never meant to be used for bots.
ts-node
is designed for REPL
purposes. That's short for Read Eval Print Loop
.
Which means to read some code, dump it in an eval()
statement, print the result, and loop.
A discord bot is not that.
A Discord bot sets up a permanent web socket connection to the Discord server and connects to the rest gateway.
There is read yes, but no eval, no print, and no loop.
So what should you use instead?
The most ideal way is to just use the watch
flag of tsc
(tsc --watch
) and run node dist/index.js
to run your bot, then cancel that process and restart it when you have changes that require restarting.
You would open 2 terminal tabs, 1 in which you run tsc --watch
and another in which you run the bot.
This is, in particular, the most ideal way, because Discord has a limit to the amount of times you can log in with your bot, or register commands, per day.
Constantly logging in over and over again due to an auto-restarting process will get you close to that limit very quickly and once you exceed it, your development will be halted entirely for the current day.
However, this can be quite tedious so a great package to use instead is tsc-watch
.I'm gonna hazzard a guess, ts-node does not load .d.ts file automatically. Possibly related.
Why for god's sake they don't no one knows