Roman Vasilev

The issue that your `BigInt.prototype.toJSON` returns bigint as number which lead to data loss.

However, ``` # Overview .footnote[2020] --- ``` Works ok. Issue can be closed, but behavior should be mentioned in documentation.

It's not fixed even in 4.6.0-dev As a quick (dirty hack) fix you can try this patch solution - https://github.com/unlight/prisma-nestjs-graphql/issues/65#issuecomment-994742228

Updated. Commenting line: // define(defaultAssert, { '__esModule': true }); fixes the problem

> Hmm. Seems that your fix conflicts with ES6 Modules / CJS / Babel interop hack. Maybe, but I just said that it fixes my problem (with SystemJS) I do...

Do you have unit tests for #28 and #37? Actually #28 has no conflicts, it is the same code: ``` js var defaultAssert = customize(); defaultAssert.default = defaultAssert; module.exports =...

I'm using NestJS with schema first approach (I tried code first, but seems it's not yet supported). Main file looks like ```js import { Module } from '@nestjs/common'; import {...

Thank you, that's worked. But NestJS's GraphQLModule `typeDefs` expects string ``` typeDefs: typeDefs.loc!.source.body, ```

Same. By design `jest.mock()` is hoisting over import. Also other methods should hoist `['mock', 'unmock', 'enableAutomock', 'disableAutomock', 'deepUnmock']` https://github.com/kulshekhar/ts-jest/blob/master/src/transformers/hoist-jest.ts

This is not an issue for me, since typescript 3.7 with [optional chaining](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-7.html#optional-chaining) feature.