Bug: Message fetch causing whole app crash when wrapped in try/catch about discord.js HOT 5 CLOSED

This function is triggered by a command, so the client is ready because it received the command - so it's not an initalisation error

from discord.js.

This appears to be a lack of JavaScript knowledge. You can learn about promises here:

• MDN
• discord.js Guide
• The Modern JavaScript Tutorial

Also for some reason the GuildBasedChannel type is missing it's MessageManager on the .messages property, even though it is infact there - hence why it has an any type to get it working.

Not all channels have message managers.

from discord.js.

Sorry, I was missing an await on the last async call due to the fact that I've spent hours trying to get fetchMessage working - however:

Not all channels have message managers.

Okay, but that channel manager clearly does have a messages property which does now work, but typescript thinks it doesn't exist at all. Not that it might be undefined or null. It literally thinks it could never possibly exist, and not even never as in never type.

The return type of channels.cache.get is supposedly GuildBasedChannel | undefined according to TS at that point

from discord.js.

And a CategoryChannel or ForumChannel does in fact not have a .messages property. You’d need to narrow the channel to one that does, preferably with the <GuildChannel>.isTextBased() typeguard.

from discord.js.

@Qjuh thank you, I didn't see anything about this in the docs, guides, or stack overflow 🙏

from discord.js.