Closed eunchurn closed 4 months ago
I found the cause. The schemaPath
is nested in the form of schemaPath.schemaPath
here. The nested schemaPath.schemaPath
appears as an absolute path. Therefore, the issue arises because path.relative()
receives to
in an object format. Consequently, on line 8, you need to change const schemaPath = await getSchemaPath0(path);
to const { schemaPath } = await getSchemaPath0(path);
.
The above issue appears to stem from the @prisma/internals
version. It seems that fixing the @prisma/internals
package to version 5.2.0
instead of using ^5.2.0
will resolve this issue.
if you are using pnpm
, add package.json
as follow
{
"pnpm": {
"overrides": {
"@prisma/internals": "5.2.0"
}
}
}
Fixed in the last version, We upgraded the Prisma version to 5.14
Steps of reproduce
@paljs/cli create
What did I do wrong?
Tested Node Versions: v22.2.0, v20.13.1