Known Issues

Known Issues#

Please look here first, to decide if it is a Typegoose or a Mongoose issue.


Never run ts-node --transpile-only or tsc --transpile-only, otherwise sometimes types are missing completly or are the wrong type.


TypeScript provides the option to alias paths (with tsconfig-paths), but is somehow incompatible with Typegoose, more info in here

Self-Containing classes#

It is currently not possible to use a self-containing class (sub-documents)

class SomeClass {
public ref: SomeClass; // ERROR "Maximum Class Stack Size Exceeded"

For References, this will work

class SomeClass {
@prop({ ref: () => SomeClass }) // or hardcode the string
public ref: Ref<SomeClass>;


Using babel as a TypeScript compiler is known to cause problems (like incorrect types)
We recommened you use tsc directly, or ts-node or ts-jest for jest-testing

If Babel is still needed, then read Babel TypeScript preset and install the following plugins: you will need to reproduce the --experimentalDecorators and --emitDecoratorMetadata TypeScript compiler options by using the corresponding plugins for enabling decorators and emitting decorator metadata:

module.exports = {
plugins: [
['@babel/plugin-proposal-decorators', { legacy: true }],

prop on get & set#

@prop cannot be applied to get & set (ES6), because virtuals do not accept options & schema.loadClass wouldn't load these.

Known Mongoose incompatibilities#


This option will NOT work, because there is no neat / simple way of defining such a thing in the same class.

Create multiple classes:

class Sub {
public name: string;
class Parent {
public subDoc: Sub;

@types/mongoose@5.7.22 and higher#

Since @types/mongoose@5.7.22, there are types for .create, but they are not fully compatible with Typegoose's types. So if an error comes up that cannot be fixed, the workaround is to use <any>

model.create<any>({ anything: anything });