mirror of
https://github.com/discordeno/discordeno.git
synced 2026-09-18 01:07:22 +00:00
FlenyandLink
e94308c8f2
Currently we import from `index.js` files where we could simply import the actual file(s) or module we need. This also creates a bit of confusion since it isn't obvious from where stuff is coming from, especially when we are importing types such as `Discord<XYZ>` types both from `@discordeno/types` and a `index.js` in the same file, one such example is `transformers/reverse/component.ts`. As far as I can tell, this does not have any specific advantage beside readability, maybe something with tree-shaking. (and for us, tree-shaking doesn't really matter) The only files that still import index.js files are: - index.js files themself - bot/src/handlers.js since it does a `import * as handlers from './handlers/index.js'` and the alternative is like 90 lines of imports Co-authored-by: Link <link20050703@gmail.com>
Discordeno
Discord API library for Node.JS, Deno & Bun
Discordeno is actively maintained to guarantee excellent performance, latest features, and ease of use.
- Simple, Efficient, and Lightweight: Discordeno is lightweight, simple to use, and adaptable.
- By default: No caching.
- Functional API:
- The functional API eliminates the challenges of extending built-in classes and inheritance while ensuring overall simple but performant code.
- Cross Runtime: Supports the Node.js, Deno, and Bun runtimes.
- Standalone components: Discordeno offers the option to have practically any component of a bot as a separate piece, including standalone REST, gateways, custom caches, and more.
- Flexibility/Scalability: Remove any properties, if your bot doesn't need them. For instance, remove
Channel.topicif your bot doesn't require it. You may save GBs of RAM in this way. A few lines of code are all that are needed to accomplish this for any property on any object.
Custom Cache
Have your cache setup in any way you like. Redis, PGSQL or any cache layer you would like.