how to get prisma in typescript

[chrisdrackett]

I've added use(prisma()) to my app.ts file, but I'm currently not seeing t.crud as being an auto complete option within a definition and also in my resolvers prisma is coming in as any. As I missing a step here?

[jasonkuhrt]

Did you enter dev mode (nexus dev)?

[chrisdrackett]

Yep, this is the command I’m using at the moment to start things. The server runs and I see everything correctly, it’s just the types in VSCode that seem off (need to run tsc to see what that does)

[jasonkuhrt]

This is really weird, if you cannot get it working, @Weakky and I would love to get on a call with you to see your context and debug live if possible? It sounds like a bug, but there could be a zillion reasons for it.

[chrisdrackett]

I'd be happy to do a call, I just refreshed my node_modules and ran everything again with the same results. I've only copied part of my app into this new project, so its pretty small at the moment.

[chrisdrackett]

where should the types for prisma stuff live? I'm curious if they are being generated in the wrong place? we have a monorepo so I wonder if that is somehow getting in the way (although it worked with nexus-schema)

[chrisdrackett]

still digging. I do have @types/typegen-nexus-prisma in my node_modules and it does seem to have the correct contents, not sure why or how it isn't getting picked up.

[chrisdrackett]

ok, I think this has to do with the fact we're using a monorepo. I noticed the following types are in node_modules within our server project:

typegen-nexus
typegen-nexus-backing-types
typegen-nexus-context

while everything else is in our main node_modules. When I move these there things work. I can probably update our tsconfig some and get this going

[jasonkuhrt]

Feel free to create an issue for better monorepo support. We haven't thought about it yet (does it work, if not, how not, etc.). We would like them to be perfectly supported.

[jasonkuhrt]

Just saw this graphql-nexus/nexus#695 btw

[chrisdrackett]

yeah, I saw that too. Seems pretty close overall, but it was easy for us to make the server not part of the monorepo (at least for now) so for us its a nice to have more than a need to have :) the need to have for us right now is getting this darn thing working on Heroku :D