Shard Manager is destroyed almost immediately
I'm using the same device, network, and bot token; bot1 starts normally but bot2 doesn't.
- bot1 is written in common js
- bot2 is written in esm + ts (mts)
- I did receive a node warning for json import assertion but removing it had no effect
- bot2's client doesn't hit the 'ready' state, and the manager destroys the client before 15s
- node v20.9.0
3 Replies
- What's your exact discord.js
npm list discord.js and node node -v version?
- Not a discord.js issue? Check out #other-js-ts.
- Consider reading #how-to-get-help to improve your question!
- Explain what exactly your issue is.
- Post the full error stack trace, not just the top part!
- Show your code!
- Issue solved? Press the button!
- ✅ Marked as resolved by OPThe package isn't the problem, the error remains the same even if i run the client alone
the "destroying shard" note prints right after the "waiting for client ready" message, doesn't wait at all
no
oh, they've stopped showing errors
thank you
true true
I've always used that
catch for killing the process.. the debug gave no clue so never thought to check it
thanks again