Module '"@prisma/client"' has no exported member 'PrismaClient'.

[thany]

Bug description

I'm getting this error in VScode after following this example's getting started steps, in the provided seed.ts file.

Other imports work just fine.
I have never used Prisma before. I'm just following the steps listed.

This problem popped up after the step npm i, which tells me either the example is set up wrong, or something specific on my computer is bollocksing up something. No idea. I assume these examples have been tested at some point, so I guess it must be something on my end. Otoh, I have never had this problem with typescript packages if they properly export their things.

How to reproduce

Literally follow this:
https://github.com/prisma/prisma-examples/tree/latest/typescript/rest-nextjs-api-routes-auth

Expected behavior

No errors.

Prisma information

I really don't think it's relevant what the schema is. If it is, please have a look at the linked example 😉

Environment & setup

• OS: Windows 10
• Database: Sqlite
• Node.js version: 16.14.0

Prisma Version

3.14.0

[thany]

Okay, so the error magically went away the next day (today, at the time of writing this). I didn't change anything in the mean time. What gives?

But now the problem is elsewhere. The PrismaClient only seems to know about users, accounts, posts, and some other guff. None of that is in my schema. Not anymore. How can I make it know about my schema? I cannot find in the documentation how to deal with this.

So for example, I've put this in the schema:

And yet:

I must be missing something. It seems as if Prisma is not able to import types from the schema. It's stuck on whatever the project was initialised with.

Update:

But, "migrating" and seeding does somehow manage to work. Making a mistake (again, I have no way to know what a mistake is if the types are completely missing) does throw an error in the CLI. So it knows about types, but doesn't expose them to typescript or something. So I basically have to guess at the types that Prisma should expose, but doesn't, and mentally ignore the potentially tonnes of errors in my project. Doesn't feel right, does it?

Suggestion: about about making schema files just plain typescript? Typescript has more than adequate facilities to transform an interface (which would be a table/model) to its CRUD functions and other supporting types. For instance, styled-components does similar typescript magic - transforming the type of one thing into several supporting types to work with that thing.

[aladinflux]

You need to generate the prisma client using prisma generate and if you're using VSCode, sometimes, it doesn't pick up the newly generated client.

I find that it helps when you cmd+click into @prisma/client so that VSCode parses the file again and updates the types.