discord.js: sodium doesn't work as of the latest version, so proposing a changeover to libsodium, which already has a JS port anyway
The sodium package discord.js is using doesn’t compile anymore due to a missing file error on the repo’s part, so I’m proposing that discord.js switches over to libsodium instead, which we’re already using the wrappers for, and won’t be an issue with the current codebase. PR #3094 dictates what this change will do to discord.js as a whole (which isn’t very much at all).
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (8 by maintainers)
@amishshah Is discord.js exclusively a Windows project?
@Monbrey @SpaceEEC @GamesProSeif @didinele The issue was closed because it compiles on Windows 10. That would imply that Windows is the only officially supported platform.
@GamesProSeif If you look back through the thread, the issue was closed on Feb 15. It being Oct 6 today did not really impact that decision.
I am aware it is an optional package and removing it was the convenient solution for encountering similar issues. Simply removing things when they don’t work on their own may work for you, but I prefer to at least attempt to investigate further when they suddenly stop working after years.
What I was trying to find out was whether or not this was the best option as a Mac user, since Windows might be the only basis for testing. I could not find any specific statement about it, but there also didn’t seem to be much concern that the issue impacted Linux, Raspberry Pi, and Mac
Anyway, thanks for your time. I think I have learned everything I need to make a decision.