We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
Can we add support for Prisma 5.17? Similar to #1536
Otherwise, I get an error when trying to install @prisma/[email protected]:
@prisma/[email protected]
npm error While resolving: [email protected] npm error Found: @prisma/[email protected] npm error node_modules/@prisma/client npm error @prisma/client@"^5.17.0" from the root project npm error npm error Could not resolve dependency: npm error peer @prisma/client@"5.0.0 - 5.16.x" from @zenstackhq/[email protected] npm error node_modules/@zenstackhq/runtime npm error @zenstackhq/runtime@"^2.3.2" from the root project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution.
Describe the solution you'd like Update dependency versions, as was done in #1541
Describe alternatives you've considered
overrides
package.json
npm install
--force
--legacy-peer-deps
Additional context None
The text was updated successfully, but these errors were encountered:
WIP 😄
Sorry, something went wrong.
Fixed in 2.3.3
No branches or pull requests
Is your feature request related to a problem? Please describe.
Can we add support for Prisma 5.17? Similar to #1536
Otherwise, I get an error when trying to install
@prisma/[email protected]
:Describe the solution you'd like
Update dependency versions, as was done in #1541
Describe alternatives you've considered
overrides
inpackage.json
npm install
with--force
or--legacy-peer-deps
Additional context
None
The text was updated successfully, but these errors were encountered: