Why do you want to contribute?
Hi Trigger.dev team,
I'm Hardik from India, and I'd like to become a long-term contributor to Trigger.dev.
I came across Trigger.dev while exploring modern TypeScript infrastructure projects and was immediately interested in the engineering challenges involved in building reliable background job systems and developer tooling. Rather than only reading the documentation, I wanted to understand the project by working directly with the codebase.
I cloned the repository, set up the development environment locally, explored the project structure, and started investigating real issues. During this process, I encountered a Windows-specific TypeScript issue affecting the @trigger.dev/database package. I spent time reproducing the issue consistently, understanding why it occurred, identifying the root cause, implementing a minimal fix, and verifying the solution locally before opening PR #4386. I later learned that contributors must first be vouched, so I read the contribution guide and decided to follow the correct process before continuing with future pull requests.
Beyond Trigger.dev, I've been actively learning open source development by contributing to large TypeScript projects such as Appwrite, where I've opened multiple pull requests and gained experience working with established codebases, project conventions, code reviews, and maintainer feedback. Working on these projects has taught me how to navigate large codebases, follow project conventions, respond to review feedback, and write focused, maintainable changes.
The type of work I enjoy most is investigating bugs, understanding root causes, improving developer experience, and making focused changes that are easy to review and maintain. I enjoy understanding why a problem occurs before proposing a fix. Trigger.dev's emphasis on TypeScript, infrastructure, developer tooling, and reliability closely matches the kind of engineering problems I enjoy solving.
I'm not looking to make a single contribution and move on. My goal is to become a consistent long-term contributor by working on well-scoped issues, learning from maintainer feedback, participating in discussions, and submitting high-quality pull requests that provide lasting value to the project and its community.
Thank you for taking the time to review my request. I appreciate the work that goes into maintaining Trigger.dev, and I'd be grateful for the opportunity to contribute and learn from the team over the long term.
Prior contributions or relevant experience
GitHub
GitHub Profile:
Trigger.dev
I explored the Trigger.dev codebase locally and investigated a Windows-specific TypeScript issue affecting the @trigger.dev/database package. After reproducing the issue, identifying the root cause, implementing a minimal fix, and verifying it locally, I opened the following pull request :
Although the pull request was automatically closed because I wasn't vouched yet, the experience helped me better understand the repository, its contribution workflow, and the importance of following the project's established process.
Appwrite
I've also been contributing to Appwrite by opening pull requests and working with a large TypeScript codebase.
Pull Requests:
Working on these projects has given me experience navigating large TypeScript codebases, following project conventions, responding to maintainer feedback, and writing focused, maintainable changes.
Technical Background
- TypeScript
- Node.js
- React
- Next.js
- PostgreSQL
- Prisma
- Docker
- GitHub Actions
- pnpm
Why do you want to contribute?
Hi Trigger.dev team,
I'm Hardik from India, and I'd like to become a long-term contributor to Trigger.dev.
I came across Trigger.dev while exploring modern TypeScript infrastructure projects and was immediately interested in the engineering challenges involved in building reliable background job systems and developer tooling. Rather than only reading the documentation, I wanted to understand the project by working directly with the codebase.
I cloned the repository, set up the development environment locally, explored the project structure, and started investigating real issues. During this process, I encountered a Windows-specific TypeScript issue affecting the
@trigger.dev/databasepackage. I spent time reproducing the issue consistently, understanding why it occurred, identifying the root cause, implementing a minimal fix, and verifying the solution locally before opening PR #4386. I later learned that contributors must first be vouched, so I read the contribution guide and decided to follow the correct process before continuing with future pull requests.Beyond Trigger.dev, I've been actively learning open source development by contributing to large TypeScript projects such as Appwrite, where I've opened multiple pull requests and gained experience working with established codebases, project conventions, code reviews, and maintainer feedback. Working on these projects has taught me how to navigate large codebases, follow project conventions, respond to review feedback, and write focused, maintainable changes.
The type of work I enjoy most is investigating bugs, understanding root causes, improving developer experience, and making focused changes that are easy to review and maintain. I enjoy understanding why a problem occurs before proposing a fix. Trigger.dev's emphasis on TypeScript, infrastructure, developer tooling, and reliability closely matches the kind of engineering problems I enjoy solving.
I'm not looking to make a single contribution and move on. My goal is to become a consistent long-term contributor by working on well-scoped issues, learning from maintainer feedback, participating in discussions, and submitting high-quality pull requests that provide lasting value to the project and its community.
Thank you for taking the time to review my request. I appreciate the work that goes into maintaining Trigger.dev, and I'd be grateful for the opportunity to contribute and learn from the team over the long term.
Prior contributions or relevant experience
GitHub
GitHub Profile:
Trigger.dev
I explored the Trigger.dev codebase locally and investigated a Windows-specific TypeScript issue affecting the
@trigger.dev/databasepackage. After reproducing the issue, identifying the root cause, implementing a minimal fix, and verifying it locally, I opened the following pull request :Although the pull request was automatically closed because I wasn't vouched yet, the experience helped me better understand the repository, its contribution workflow, and the importance of following the project's established process.
Appwrite
I've also been contributing to Appwrite by opening pull requests and working with a large TypeScript codebase.
Pull Requests:
Working on these projects has given me experience navigating large TypeScript codebases, following project conventions, responding to maintainer feedback, and writing focused, maintainable changes.
Technical Background