You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dev release of discordjs ([email protected]) points to @discordjs/[email protected] instead of @discordjs/[email protected] (most likely it's intended, but it would fix my problem). @discordjs/[email protected] doesn't include fix for invalid protocol value fixed in #10271
I can go around this problem locally, but it's very problematic for "serverless" functions running on deno to go around this problem :/
I am not aware of the current scope for the next release, but I would like to ask for a bugfix publish-release which contains previously-mentioned PR with bumped-up versions
Code sample
No response
Versions
As described above
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable
Which gateway intents are you subscribing to?
Not applicable
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered:
Which package is this bug report for?
discord.js
Issue description
Dev release of discordjs (
[email protected]
) points to@discordjs/[email protected]
instead of@discordjs/[email protected]
(most likely it's intended, but it would fix my problem).@discordjs/[email protected]
doesn't include fix for invalid protocol value fixed in #10271I can go around this problem locally, but it's very problematic for "serverless" functions running on deno to go around this problem :/
I am not aware of the current scope for the next release, but I would like to ask for a bugfix publish-release which contains previously-mentioned PR with bumped-up versions
Code sample
No response
Versions
As described above
Issue priority
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable
Which gateway intents are you subscribing to?
Not applicable
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: