Skip to content
New issue

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

[Feature Request] Prisma 5.17 support #1598

Closed
tony19 opened this issue Jul 19, 2024 · 2 comments
Closed

[Feature Request] Prisma 5.17 support #1598

tony19 opened this issue Jul 19, 2024 · 2 comments
Milestone

Comments

@tony19
Copy link

tony19 commented Jul 19, 2024

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]:

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 in package.json
  • npm install with --force or --legacy-peer-deps

Additional context
None

@ymc9
Copy link
Member

ymc9 commented Jul 19, 2024

WIP 😄

@ymc9 ymc9 added this to the v2.3.x milestone Jul 19, 2024
@ymc9
Copy link
Member

ymc9 commented Jul 19, 2024

Fixed in 2.3.3

@ymc9 ymc9 closed this as completed Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants