With TypeScript, this does not really work well. Especially due to missing events where you removed most of them.

With TypeScript, this does not really work well. Especially due to missing events where you removed most of them.

the removed events are inherited from the discord.js Client class

With TypeScript, this does not really work well. Especially due to missing events where you removed most of them.

the removed events are inherited from the discord.js Client class

When I tried it, I did not have any type-hinting for events.

With TypeScript, this does not really work well. Especially due to missing events where you removed most of them.

the removed events are inherited from the discord.js Client class

When I tried it, I did not have any type-hinting for events.

this could be being caused by line 201, ill test this at some point and see

edit: i remember something a while back about the generic string type, essentially, remvoing all the autocompletes from ts

I get type-hinting for the events listed there, for example, commandBlock. However, with this change, I lost the ability to get hints for events like presenceUpdate or messageUpdate.

@ShawnCZek fixed

Hey team I'm still getting errors at compile time using the latest discord.js package which seem to relate to this:

Property 'reply' in type 'CommandoMessage' is not assignable to the same property in base type 'Message'. Type '{ (content: any, options?: MessageEmbed | MessageAttachment | (MessageEmbed | MessageAttachment)[] | (MessageOptions & { ...; })): Promise<...>; (content: any, options?: MessageEmbed | ... 2 more ... | (MessageOptions & { ...; })): Promise<...>; }' is not assignable to type '{ (content: string | number | bigint | boolean | symbol | readonly any[] | MessageEmbed | MessageAttachment | (MessageEmbed | MessageAttachment)[] | (MessageOptions & { ...; })): Promise<...>; (options: MessageOptions & { ...; }): Promise<...>; (options: APIMessage | MessageOptions): Promise<...>; (content: any, opt...'. Type 'Promise<CommandoMessage>' is not assignable to type 'Promise<Message>'. Type 'CommandoMessage' is not assignable to type 'Message'. The types returned by 'reply(...)' are incompatible between these types. Type 'Promise<CommandoMessage>' is not assignable to type 'Promise<Message[]>'. Type 'CommandoMessage' is missing the following properties from type 'Message[]': length, pop, push, concat, and 26 more.

Anyone got any ideas?

I can confirm the latest Commando master works with discord.js 12.2.0, but not with the latest discord.js master

This would be because discord.js master has switched to using discords new inline replies which will require similar changes to Commando

I haven't figured out what the most recent compatible version of discord.js is yet, I'll keep checking.

Looks like Commando works up to discord.js 12.3.1, but isn't compatible with 12.4.0 onwards.

If someone more knowledgeable about TypeScript would like to tackle this, feel free. My knowledge of it is zilch.

Can you somehow unmerge this or something, its impossible to write a command in typescript properly. None of my old bots work and I have had to rollback to an oudated version so they would run. Please.

And the issue that comes from this PR is...?

why revert it when you can fix it

#355