nexus-plugin-prisma: Getting error: Expression produces a union type that is too complex to represent

+1

I was still receiving the error after downgrading to ts 3.4.5, however, I realized VS code was using its own version of typescript instead of my project’s. To fix, I ran the command palette (shift+cmd+p) and typed in “Select Typescript Version”. You would then select your workspace or project typescript version rather than vscode’s.

I am running into this exact error. My code:

const User = prismaObjectType({
  name: "User",
  definition(t) {
    t.prismaFields(["name", "id", "avatarUrl"]);
  }
});

I downgraded to 3.4.5 and also changed TS version in vscode (vsc does allow to change ts version even in 1.36.1) and now it’s working for me

This might work:

export const Department = prismaObjectType<'Department'>({
  name: 'Department',
  definition(t) {
    t.prismaFields(['*'])
  },
})

I’m getting this too! In the mean time I fixed it by rolling back typescript to 3.4

    "typescript": "3.4"

Installing Typescript 3.4.5 into my package.json and using the workspace’s typescript for my project in VS Code solved this problem for me.

If your not sure how to change your VS Code TypeScript version to use your workspace, here is a great stack overflow post explaining how to do this.

https://stackoverflow.com/questions/39668731/what-typescript-version-is-visual-studio-code-using-how-to-update-it

when I use Typescript 3.7.5 it was nothing error like this issue, but now, I update latest Typescript 3.8.2 I got this error

I’m in the same position as @blackxored and I can’t update to prisma2 due to this issue https://github.com/prisma/prisma2/issues/254 … Pls fix

Any updates on this? Still present on 3.6.x. Locking 3.4 for now but fp-ts requires 3.5 so I’m in for a world of pain.

The server is start correctly, but build doesn’t work. and ts version is 3.4.5

ts version 3.4.5 works for me.

Latest VScode (1.37) uses 3.5.2 by default, remember to switch to workspace version for using ts 3.4.5

Btw, the problem also exist in the new ts version 3.6, seems we need to lock ts version at 3.4.x until this issue is fixed…

@darrylyoung Yes, they are moving fast!

My primary development project uses Prisma 1 before Nexus or even the generated Prisma Client. That version of Prisma has been rock solid, but it’s time to update for new development. I expect to rebuild that server pretty much from scratch using prisma 2.

The only examples at prisma/photon that use nexus-prisma are graphql and graphql-auth.

I’m just getting started with Prisma2, and it’s going well so far. The best advice I can give is to look to the prisma/photon project for examples. All the other stuff (including nexus-prisma with prisma2 preview) is out of date regarding Prisma2. At least I was unable to get it working. but the prisma/photon examples worked pretty much “out of the box”.

@ar1a Thanks for that 😃 Configuring dependency versions as you have them, deleting node_modules and re-installing did not resolve the issue for me.

However, I cloned your project, opened server/resolvers/Mutations.ts and .../Queries.ts and the error does not appear. (still scratching head)

My project is from the ‘Prisma Getting Started’ tutorial.

Glad I’m not alone here as I’m also having the same problem.

My TypeScript-related dependencies are:

"devDependencies": {
  "ts-node": "^8.3.0",
  "ts-node-dev": "^1.0.0-pre.39",
  "typescript": "^3.5.2"
}

My Nexus-related dependencies are:

"dependencies": {
  "graphql": "^14.3.1",
  "graphql-yoga": "^1.17.4",
  "nexus": "^0.11.7",
  "nexus-prisma": "^0.3.7",
  "prisma-client-lib": "^1.34.0"
},

Hi there!

Having the same issue for a few days on compilation, and now even vs code throws me errors with the typescript linter since this morning (the last update of vs code).

My colleague doesn’t have this issue because he didn’t upgrade VS Code to 1.35.1.

But in my vs code, I have:

And when I hover it, I get the following error:

Expression produces a union type that is too complex to represent. ts(2590)

The ts-node index.ts command throws me the same error.

However, my application compiles perfectly with ts-node-dev. No issue on that side.

My config:

• nexus: ^0.12.0-beta.6
• nexus-prisma: ^0.3.7
• ts-node: ^8.2.0
• ts-node-dev: ^1.0.0-pre.40
• typescript: ^3.5.2

Odd, I’ve had the same issue at times while running ts-node-dev and instead end up running nodemon ts-node [file] to success.

same issue with typescript 3.5.1