Custom output path behaves different with `prismaSchemaFolder` preview feature about prisma HOT 10 OPEN

This has created an issue for me:

If I use a custom output path (even after removing a ../). I get an error telling me that the module can't be found in compile time. However, intellisense is working. And when I visit the location, I can see the correct files.

If I remove the custom output path, the app gets compiled.

from prisma.

I faced the same issue

from prisma.

Do I understand correctly that moving your Prisma Schema from ./prisma/schema.prisma to ./prisma/schema/foo.prisma and ./prisma/schema/bar.prisma leads to the output value still being evaluated relative to ./prisma instead of ./prisma/schema?

from prisma.

Do I understand correctly that moving your Prisma Schema from ./prisma/schema.prisma to ./prisma/schema/foo.prisma and ./prisma/schema/bar.prisma leads to the output value still being evaluated relative to ./prisma instead of ./prisma/schema?

it not work too.

from prisma.

@janpio yes, you are right.

from prisma.

This has created an issue for me:

If I use a custom output path (even after removing a ../). I get an error telling me that the module can't be found in compile time. However, intellisense is working. And when I visit the location, I can see the correct files.

If I remove the custom output path, the app gets compiled.

Using Custom Output Path

Generator

Files inside @prisma/client

Prisma Client Service in NestJS

Error

However, if I omit the custom output path, it works fine

from prisma.

@xudo49 Please open a new discussion or issue for your problem, it does not sounds related to this one. Thank you.

from prisma.

@vimulatus Generally generating into node_modules manually and especially node_modules/@prisma/client might not be the best idea, as the behavior of this is pretty much undefined with custom output. Usually you would probably be better off choosing a defined path in your project.

That being said, that does not explain the error you are getting. Can you delete your node_modules, and then re-install them and run prisma generate to double check if it creates your generated Prisma Client in the correct place? Did you look into that master folder to make sure there is the correct stuff that should be there?

from prisma.

@janpio I've checked it before and yes, it's generate Prisma Client in the correct place.

from prisma.

It seems that the path finding for output in Prisma Schema is currently not as expected with prismaSchemaFolder. It still seems to use ./prisma as the source, even when you moved your ./prisma/schema.prisma to ./prisma/schema/*.prisma. It is clearer that this is invalid when you actually have a custom schema folder path like --schema foo/bar and all your files are in foo/bar/*.prisma - then the output seems to currently be relative to foo.

We might need to revisit this, and either use the schema folder as the folder to be relative to, or even more correct the file (as in theory the file with the output definition could also be in a subfolder of the schema folder).

from prisma.