michallytek/type-graphql

Create GraphQL schema and resolvers with TypeScript, using classes and decorators!

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 8th, 2026
Created on January 9th, 2018
Open Issues & Pull Requests: 120 (+0)
GitHub issues: Enabled
Number of forks: 672
Total Stargazers: 8,092 (+0)
Total Subscribers: 61 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 999 days
Stale 30+ days: 23
Stale 90+ days: 20

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Community :family_man_girl: (28)
  • Enhancement :new: (13)
  • Discussion :speech_balloon: (8)
  • Documentation :book: (7)
  • Question :grey_question: (7)
  • Need More Info :man_shrugging: (6)
  • Solved :heavy_check_mark: (6)
  • Bug :bug: (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

TypeGraphQL is a framework for building GraphQL APIs using TypeScript classes and decorators to define schema and resolvers.

TypeGraphQL addresses the redundancy problem that arises when developing GraphQL APIs in Node.js with TypeScript. Traditionally, developers must maintain separate GraphQL SDL schema definitions, ORM entity classes, and TypeScript interfaces for arguments and inputs, creating multiple sources of truth that easily fall out of sync. The framework consolidates this by using TypeScript classes as the single source of truth, with decorators marking fields, types, inputs, and resolvers. This approach eliminates the need to manually keep schema files, models, and interfaces synchronized and enables IDE features like rename refactoring to work correctly across the entire codebase.

Developers should choose TypeGraphQL if they are building GraphQL APIs in TypeScript and want to reduce boilerplate and maintenance overhead. It suits projects where keeping schema definitions aligned with data models is a priority and where features like dependency injection, validation, and authorization guards are needed. The README positions the tool as an improvement over code generation approaches like GraphQL Code Generator, which only generate interfaces from an existing schema rather than eliminating the schema-model redundancy problem entirely.

The project maintains active development with regular updates and engagement with the community. The codebase shows consistent refinement of core functionality and ongoing attention to user-reported issues. Documentation is comprehensive and well-maintained, with a dedicated website providing detailed API reference and tutorials. The project demonstrates stability through its established patterns and conventions for common GraphQL development tasks.