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

Support for Prisma 6 #475

Open
RubenNL opened this issue Nov 29, 2024 · 7 comments · May be fixed by #476
Open

Support for Prisma 6 #475

RubenNL opened this issue Nov 29, 2024 · 7 comments · May be fixed by #476
Assignees
Labels
community Something initiated by the community enhancement New feature or request help wanted Extra attention is needed priority:high This issue is important and will be done first

Comments

@RubenNL
Copy link

RubenNL commented Nov 29, 2024

Is your feature request related to a problem? Please describe.

Prisma version 6 has been released, which causes this warning:

Looks like an incorrect version "6.0.0" of the Prisma packages has been installed. 'typegraphql-prisma' works only with selected versions, so please ensure that you have installed a version of Prisma that meets the requirement: "^5.18.0". Find out more about that requirement in the docs: https://prisma.typegraphql.com/docs/basics/prisma-version

Bypassing this warning with SKIP_PRISMA_VERSION_CHECK=true works fine for my application, but I don't know if this is the same for everyone.

Describe the solution you'd like

For me, just updating the package.json version should be enough.

Describe alternatives you've considered

Additional context

https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6#breaking-changes

@FezVrasta FezVrasta linked a pull request Dec 9, 2024 that will close this issue
@marticrespi
Copy link

Any update about it?

@cesarvspr
Copy link

Unfortunately, this is a significant reason not to use this tool. I understand that the maintainer is not obligated to fix every issue, but this is an important feature. It would be great to leave some tips for anyone with the bandwidth to contribute and help improve it.

@MichalLytek
Copy link
Owner

@cesarvspr Please make sure you're up to the statement here:
#385

The reality is that I don't use this tool anymore on my daily-basis at work, so I don't have the urge to dedicate my personal time for supporting this project anymore. Prisma abandoned sponsorship some time ago, and the sponsorship was the only reason I started this project.

So yes, without a help of community, there's no future for this project. However, maintaining compatibility with new Prisma releases is not so complex, so it shouldn't be an issue to make one or two releases a year.

If someone is willing to spend some time on actual digging in the code, fixing the tests after bumping dependencies, feel free to reach me if you need some help, assist or guide.

If you only want to yell and complain, there's nothing I can do for you.

@MichalLytek MichalLytek added enhancement New feature or request help wanted Extra attention is needed priority:high This issue is important and will be done first community Something initiated by the community labels Jan 16, 2025
@cesarvspr
Copy link

@MichalLytek Thank you for clarifying, and I’m sorry if my message came across the wrong way. I didn’t mean to yell or complain, and I completely understand your situation. My intention was simply to ask if there might be any guidance or information that could help anyone in the community who has the bandwidth to contribute. I truly appreciate the work you’ve put into this project and your willingness to assist others who want to take it forward.

@jbdoster
Copy link

My workaround for now is overriding the dependencies using prisma 5.22.0:

package.json

  "pnpm": {
    "overrides": {
      "typegraphql-prisma": "npm:@prisma/client@5.22.0",
      "typegraphql-prisma": "npm:prisma@5.22.0"
    }
  }

@marticrespi
Copy link

@jbdoster Can you share your whole package.json? I get a duplicate key error

Image

Thanks!

@PS1TD
Copy link

PS1TD commented Mar 24, 2025

Also interested on how to do the override
Getting this error

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Something initiated by the community enhancement New feature or request help wanted Extra attention is needed priority:high This issue is important and will be done first
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants