I’m seeking community/contributor help to refine the API design for @tego/bot—a core package in our monorepo that aims to provide a simple, intuitive automation API for Node.js (with future Deno/Bun support).
Our top priority is an API that’s easy to adopt (minimal boilerplate, self-documenting) while being flexible enough for enterprise use cases.
Core Goals for the API
- Ease of Use: Developers should write automations in 1–2 lines of code for common tasks (e.g., run a CLI command, sync data with Tego).
- Cross-Runtime Compatibility: Design that works seamlessly with Node.js, Deno, and Bun (no breaking changes when porting).
- Modularity: Allow extending with plugins (e.g., Tego-specific integrations, third-party tools like Slack/Google Sheets).
- Performance: Leverage aumate’s native bindings without exposing complexity to end-users.
I’m seeking community/contributor help to refine the API design for @tego/bot—a core package in our monorepo that aims to provide a simple, intuitive automation API for Node.js (with future Deno/Bun support).
Our top priority is an API that’s easy to adopt (minimal boilerplate, self-documenting) while being flexible enough for enterprise use cases.
Core Goals for the API