Problem with Prisma 3.12.0 running nestjs/cli@8.2...
# orm-help
c
Problem with Prisma 3.12.0 running nestjs/cli@8.2.0 with node-windows@1.0.0-beta.7 and nodejs v14.17.6 Start service with node-windows works fine with Prisma 3.11.1 - but as soon as I upgraded to Prisma 3.12.0 - node-windows would run, but the service wouldn't start. Error 1067. Reinstalled Prisma 3.11.1 and node-windows service starts as expected.
n
Hey 👋 So you are able to run
@prisma/client
v3.11.1 without any issues, but upgrading to v3.12.0 causes your service to not start. Correct?
c
Yes, but I am still researching the issue. I hope to have more information by EOD today.
👍 1
OK, found out this has to do with node-windows@node-windows@1.0.0-beta.7 My project was running prisma/client@3.11.1 node-windows@1.0.0-beta.6 upgraded both prisma/client@3.12.0 node-windows@1.0.0-beta.7 When I attempt to start windows service, the service would create, but fail to start (manual start returns error: 1067). Sorry, this isn't a Prisma issue.
👍 1
My project is working with nestjs/cli@8.2 prisma/cli@3.12.0 node-windows@1.0.0-beta.6 Windows service will not start with node-windows@1.0.0-beta.7
🙌 1