Separate MeganeBot and MeganeClient
Open
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
MeganeBot and MeganeClient are currently in the same module, but they are effectively their own module that shares a common package.json.
Since MeganeBot has a one-way dependency on MeganeClient, once MeganeBot has more crazy features, we should split them up.
First they should be in their own module, then we can figure out if there is any need to separate them into their own repos.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.