Updated to the latest `nexus-plugin-prisma@0.24.0`...
# graphql-nexus
a
Updated to the latest
nexus-plugin-prisma@0.24.0
and running
makeSchema
is now giving me the error
Copy code
nexus-plugin-prisma/src/dmmf/transformer.ts:55
    inputTypes: schema.inputTypes.map((type) => transformInputType(type, globallyComputedInputs, atomicOperations)),
                                  ^
TypeError: Cannot read property 'map' of undefined
    at transformSchema (node_modules/nexus-plugin-prisma/src/dmmf/transformer.ts:55:35)
    at transform (node_modules/nexus-plugin-prisma/src/dmmf/transformer.ts:30:13)
    at Object.exports.getTransformedDmmf (node_modules/nexus-plugin-prisma/src/dmmf/transformer.ts:17:37)
    at new SchemaBuilder (node_modules/nexus-plugin-prisma/src/builder.ts:267:7)
    at Object.build (node_modules/nexus-plugin-prisma/src/builder.ts:185:19)
    at Object.onInstall (node_modules/nexus-plugin-prisma/src/plugin.ts:46:62)
    at node_modules/@nexus/schema/src/builder.ts:663:44
    at Array.forEach (<anonymous>)
    at SchemaBuilder.beforeWalkTypes (node_modules/@nexus/schema/src/builder.ts:657:18)
    at SchemaBuilder.getFinalTypeMap (node_modules/@nexus/schema/src/builder.ts:798:10)
r
@Adam cannot reproduce this one. I’m using it in this repo and it works fine.
a
@Ryan I can reproduce the failure on that codebase if you bump the @nexus/cli and @nexus/client to
2.12.0
I know technically you get the warning that 2.10.x and 2.11.x are the only supported versions but I saw on here before that when a new version comes out that the warning can lag
r
I guess you mean Prisma, I would wait till Nexus has official support for Prisma and as we run E2E tests across each version and new updates might break stuff.
a
oh, I thought nexus and prisma were just different projects under the same entity
r
The projects are different, and released separately, but we are looking to synchronize that in the near future.
šŸ™ 1
a
gotcha
d
Can confirm this problem on @prisma/client 2.12.0
šŸ‘ 1
d
I can also confirm that I’m seeing this issue after upgrading to 2.12.0 from 2.11.0.
šŸ‘ 1
d
+1