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

@prisma/internals >= 5.15.0 missing getSchemaPath - breaks utils package #334

Closed
jacobclarke92 opened this issue Jun 7, 2024 · 3 comments

Comments

@jacobclarke92
Copy link

Just a heads up since they added multi-file schema support it looks like the getSchemaPath function isn't exported from @prisma/internals anymore.

Was getting this error before I realised what was going on, and eventually traced it back to the utils package.

    TypeError: (0 , internals_1.getSchemaPath) is not a function

Oddly enough after I downgraded all prisma packages to 5.14.0 (and explicitly installed the internals package to devDeps),
I ended getting a different error message:

    TypeError: The "to" argument must be of type string. Received an instance of Object
    Code: ERR_INVALID_ARG_TYPE

I kind of suspect pnpm store shenanigans but am honestly not too sure.
Anyway it's still a breaking change that'll need to be updated somehow, am just in the middle of wrapping up a work week but might come have a look later if you want assistance?

@AhmedElywa
Copy link
Collaborator

Thanks for letting me know about this breaking change.

You should use our last version with prisma 5.14.

The error you face with to argument you have an issue with your version in pnpm I worked with it and working fine.

@eunchurn
Copy link

When using version 5.14, pnpm installs @prisma/internal version 5.9. Therefore, in my case, fixing the @prisma/internal version as shown below resolved the error. In version 5.15, the same error occurs in paljs 7.0.0.

{
  "pnpm": {
    "overrides": {
      "@prisma/internals": "5.14.0"
    }
  }
}

@AhmedElywa
Copy link
Collaborator

Please use the prisma 5.16 and paljs 7.0.1 and will fix that for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants