Argument of type '"stateChange"' is not assignable to parameter of type 'VoiceConnectionStatus.Signalling'

Which package is this bug report for?

voice

Issue description

1. Copy this repo: https://github.com/kaaaxcreators/Discord-MusicBot/tree/develop
2. Then try to build it
3. Typescript Error: Argument of type '"stateChange"' is not assignable to parameter of type 'VoiceConnectionStatus.Signalling' here: https://github.com/kaaaxcreators/Discord-MusicBot/blob/f86381c6988348ca32d55ff1e383caf179d2e387/src/util/Music.ts#L61 and here https://github.com/kaaaxcreators/Discord-MusicBot/blob/f86381c6988348ca32d55ff1e383caf179d2e387/src/util/Music.ts#L122

Code sample

https://github.com/kaaaxcreators/Discord-MusicBot/blob/develop/src/util/Music.ts
(Its the discord/voice Music Bot example fitted to my needs)

Package version

0.8.0

Node.js version

16.13.2, 4.6.2

Operating system

Windows 10 21H1

Priority this issue should have

Medium (should be fixed soon)

Which partials do you have configured?

Channel

Which gateway intents are you subscribing to?

Guilds, GuildEmojisAndStickers, GuildVoiceStates, GuildMessages, GuildMessageReactions, DirectMessages, DirectMessageReactions

I have tested this issue on a development release

No response

[Crawron]

Happens to me as well. Issue seems to be on the second half of AudioPlayerEvents and VoiceConnectionEvents.

} & {
    [status in VoiceConnectionStatus]: (oldState: VoiceConnectionState, newState: VoiceConnectionState & {
        status: status;
    }) => Awaited<void>;
};

Changing the line status: status; on both AudioPlayerEvents and VoiceConnectionEvents to be a conditional type like below fixes the issue, as far as I can tell.

} & {
    [status in VoiceConnectionStatus]: (oldState: VoiceConnectionState, newState: VoiceConnectionState & {
        status: status extends VoiceConnectionStatus ? status : VoiceConnectionStatus;
    }) => Awaited<void>;
};

Should I PR this change?

[Zhincore]

I have similar issue

The following snippet has the problem:

player.on("stateChange", (oldState, state) => {
  /*...*/
});

But this one doesn’t throw any error:

player.on("stateChange", () => {
  /*...*/
});

The workaround is following:

player.on<"stateChange">("stateChange", (oldState, newState) => {
  /*...*/
});

I assume the parameters somehow infer different type than “stateChange”.