Seems like at least the last few versions of `@pri...
# orm-help
w
Seems like at least the last few versions of
@prisma/engine-core
depend on a version of the Undici module, but specifically reference a commit on github instead of a version packed in NPM. Our corp environment means we can't actually install prisma in our CI/CD pipelines because of this, as all dependencies must be on NPM. Seems the referenced commit is now in a mainline release of the undici module. Can this be changed to reference a versioned number?
✔️ 1
j
Hi Wade! Indeed we wanted to clean that up and were waiting for the 2.0 version so I’ll upgrade to the npm tag 2.0.2 for undici
w
thanks so much
👍 1
j
It will be part of the next official release 🙂 (Will also be in our dev tag sooner but I would not recommend to use it production)
w
any idea of timing?
j
Yes every 2 weeks we cut a release on Tuesday, so Tuesday 29th
w
great thanks
💯 1
but yeah general feedback that direct git dependencies in npm are a showstopper for us, and I imagine others as well, and prevents us from moving forward with our deployment
👍 1
j
Feedback received and will try to avoid in the future - better to publish our own fork to Npm although it adds a few steps.
💯 1
w
thanks for keeping it in mind
j
Hi @Wade Tandy! We updated the undici dependency with the latest npm version, so that should fix your problem. Let us know what you think of this 2.8.0 release 😉 https://github.com/prisma/prisma/releases/tag/2.8.0