New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Discord.js V13 #48
Comments
Hello! When Do you need it in a near future? I don't know if we can support both versions easily. |
I would like to have it in the future, but I don't need it ASAP. I can wait until v13 becomes a stable release. I don't currently need support for v13, since production code is still written in v12. As for now, I have temporarily disabled the tic-tac-toe command for my bot's development for v13 of discord.js. |
As the version 13 of discord.js is now out, I started to look into it. But I'm quite disappointed that it only supports Node 16+ which is not a LTS version. My module is intended to be easily installable and ready-to-use for all the community, so I can't make Node 16 mandatory for now. And I don't quite agree with the way the discord.js creators think. Check the discussion about it on their repository: discordjs/discord.js#5119
BUT I will try to add support for both v12 and v13 and fix the bug you mentionned. |
Ah okay, thanks for the update. I do want to mention one thing I forgot, in case you haven't added it in the prototype; I am listening to interaction events instead of message events, which means that you would have to take in account for both slash commands and/or regular messages. |
I have just wrote a new issue on this subject yes! Check it here: #56 |
Hello! Node.js 16 is out as a LTS version! 👍 Here is how I have planned to handle module versionning:
This versionning schedule is temporary and may change according to user needs. |
Version 3 of the module is now out with discord.js v13 support! |
Any plans for making this compatible with discord.js version 13 that is currently in development? When I try to react to the message, nothing happens.
The text was updated successfully, but these errors were encountered: