Commands + Listeners not registering

My commands and listeners are not registering/running. I suspect its because I'm using tsx but am not sure what the best way to resolve it would be
6 Replies
Solution
TheeDeer
TheeDeer9mo ago
No description
TheeDeer
TheeDeer9mo ago
No description
djoh the III
djoh the III9mo ago
afaik the main entry in package.json should point to the folder with transpiled files, e.g. dist/index.js
Favna
Favna9mo ago
:this: Decide between tsx or tsc. Don't mix them. Use tsc-watch if you want to watch and reload. Latter blurb of
Spinel
Spinel9mo ago
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.
Want results from more Discord servers?
Add your server