Oliver St.
06/13/2022, 11:18 AMERR_PNPM_BAD_PACKAGE_JSON ****/pnpm-workspace-template/libs/prisma/node_modules/@prisma/client/package.json: Invalid name: “.prisma/client”
So pnpm doesn’t allow package names starting with a dot .
Does a fix exist or is this a new issue?Richard Ward
06/13/2022, 11:44 AMoutput
in the generate client
in your prisma.schema
file:
generator client {
provider = "prisma-client-js"
output = "../node_modules/.prisma/client"
}
https://github.com/prisma/prisma/issues/13672#issuecomment-1152581890Oliver St.
06/13/2022, 12:04 PMoutput = "../node_modules/@prisma/client"
This is no problem, the folder structure is correct, but the generated package.json `name`value is .prisma/client
-> pnpm references this as bad package name and failsRichard Ward
06/13/2022, 12:11 PM7.2.1
and do not get that errorRichard Ward
06/13/2022, 12:12 PMsrc/layers/prisma/node_modules/@prisma/client/package.json
has the following at the top:
{
"name": "@prisma/client",
"version": "3.15.1",
Richard Ward
06/13/2022, 12:13 PMOliver St.
06/13/2022, 12:18 PMRichard Ward
06/14/2022, 5:32 AMgenerator client {
provider = "prisma-client-js"
output = "../node_modules/.prisma/client"
}
Richard Ward
06/14/2022, 5:32 AMschema.prisma
file