Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time
September 11, 2023 13:20
September 24, 2019 16:42
September 1, 2019 01:53
August 2, 2019 19:06
September 1, 2023 13:24
September 1, 2023 13:24


(These badges are from typegoose:master)
Node.js Tests npm

Define Mongoose models using TypeScript classes


Migration Guides:
(Date format: dd-mm-yyyy)

  • 10 to 11 (released on 27-03-2023)
  • 9 to 10 (released on 12-12-2022)
  • 8 to 9 (released on 22-09-2021)
  • 7 to 8 (released on 28-07-2021)
  • 6 to 7 (released on 01-04-2020)
  • 5 to 6 (released on 30-09-2019)

Basic usage

import { prop, getModelForClass } from '@typegoose/typegoose';
import * as mongoose from 'mongoose';

class User {
  public name?: string;

  @prop({ type: () => [String] })
  public jobs?: string[];

const UserModel = getModelForClass(User); // UserModel is a regular Mongoose Model with correct types

(async () => {
  await mongoose.connect('mongodb://localhost:27017/', { dbName: 'test' });

  const { _id: id } = await UserModel.create({ name: 'JohnDoe', jobs: ['Cleaner'] });
  const user = await UserModel.findById(id).exec();

  console.log(user); // prints { _id: 59218f686409d670a97e53e0, name: 'JohnDoe', __v: 0 }


A common problem when using Mongoose with TypeScript is that you have to define both the Mongoose model and the TypeScript interface. If the model changes, you also have to keep the TypeScript interface file in sync or the TypeScript interface would not represent the real data structure of the model.

Typegoose aims to solve this problem by defining only a TypeScript interface (class), which needs to be enhanced with special Typegoose decorators (like @prop).

Under the hood it uses the Reflect & reflect-metadata API to retrieve the types of the properties, so redundancy can be significantly reduced.

Instead of writing this:

// This is a representation of how typegoose's compile output would look like
interface Car {
  model?: string;

interface Job {
  title?: string;
  position?: string;

interface User {
  name?: string;
  age!: number;
  preferences?: string[];
  mainJob?: Job;
  jobs?: Job[];
  mainCar?: Car | string;
  cars?: (Car | string)[];

const JobSchema = new mongoose.Schema({
  title: String;
  position: String;

const CarModel = mongoose.model('Car', {
  model: string,

const UserModel = mongoose.model('User', {
  name: { type: String },
  age: { type: Number, required: true },
  preferences: [{ type: String }],
  mainJob: { type: JobSchema },
  jobs: [{ type: JobSchema }],
  mainCar: { type: Schema.Types.ObjectId, ref: 'Car' },
  cars: [{ type: Schema.Types.ObjectId, ref: 'Car' }],

You can just write this:

class Job {
  public title?: string;

  public position?: string;

class Car {
  public model?: string;

class User {
  public name?: string;

  @prop({ required: true })
  public age!: number; // This is a single Primitive

  @prop({ type: () => [String] })
  public preferences?: string[]; // This is a Primitive Array

  public mainJob?: Job; // This is a single SubDocument

  @prop({ type: () => Job })
  public jobs?: Job[]; // This is a SubDocument Array

  @prop({ ref: () => Car })
  public mainCar?: Ref<Car>; // This is a single Reference

  @prop({ ref: () => Car })
  public cars?: Ref<Car>[]; // This is a Reference Array

Extra Examples

Requirements & Install

Typegoose's Quick Start Guide


yarn install
yarn run test


This Project should comply with Semver. It uses the Major.Minor.Fix standard (or in NPM terms, Major.Minor.Patch).

Join Our Discord Server

To ask questions or just talk with us, join our Discord Server.


Known Issues

Here are the known-issues


Here is the FAQ


  • Please don't add +1 or similar comments to issues. Use the reactions instead.