[refactor]: Migrate Project from JavaScript to TypeScript
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Problem
The codebase currently lacks compile-time type safety, making refactors and API integrations riskier.
### Proposed Work
- Set up TypeScript compiler configuration and build scripts.
- Migrate bot entrypoint, commands, events, and database modules from `.js` to `.ts` incrementally.
- Add strict typing for Discord interactions, command interfaces, and DB models.
- Update linting/format tooling and npm scripts for TypeScript workflow.
### Acceptance Criteria
- Project builds successfully with `tsc` and runs in development/production.
- Core modules (`index`, `commands`, `events`, `database`) are migrated to TypeScript.
- No `any`-heavy implementation in critical paths without documented justification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing index, commands, events, and database modules along with the npm scripts, then run tsc as the TypeScript workflow is introduced. Done means the core modules are migrated, the project builds and runs in development and production, and critical paths avoid undocumented any-heavy typing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- backend, build-system, databases, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100