nexus-prisma types undefined when deploying to heroku #108
Comments
chrishoermann
changed the title
|
This might be because the prisma client and nexus were not successfully built, because of #107 |
|
Facing the same issue. Attaching my build log and application log build log application log |
|
As a workaround installing all dependencies in heroku and building again helped me Procfile: |
|
@MikeYermolayev Indeed the generator is running, yet somehow your runtime does not have the result of that generated code. Is there a way you can share what code is actually running? Not sure how helpful that info will be though. After the build step, it seems that Heroku is not pulling in the modified version of Maybe there is a caching issue of some sort. However, wonder why I would be open to allowing users to customize where the nexus-prisma generated runtime is emitted to. However, that would add complexity for users and I want to only do that once we understand there is no other option. |
jasonkuhrt
added
the
needs/discussion
|
Getting the same error. thought I was doing something wrong first time using nexus. anything I can provide to help? |
|
@maks112v If you can share a repro-repo with that would help. More minimal the better. I can then setup my own heroku app to run it and see the repro. |
|
https://www.dropbox.com/s/kh982dy2xrcgat0/api.zip?dl=0 |
|
The issue seems connected with https://devcenter.heroku.com/articles/troubleshooting-node-deploys#missing-modules I doubt any actions are expected from nexus-prisma team except maybe adding to to troubleshoot section |
|
@MikeYermolayev did you install |
|
Thanks @maks112v will try to look soon but might be a few weeks. |
|
No. It's installed as dependency. no idea why it gets pruned |
|
Running into a potentially similar issue as well: |
|
@trey-m do you have a repro for that I can look at? |
Manually run prisma generate after installing your dependencies as a workaround. |
I currently have a postinstall script that runs prisma generate.
Update: This issue was on my end. Sorry for raising a false flag. |
|
Seeing the same issue during a docker build where removing the part that prunes dev-dependencies fixes the issue. nexus-prisma is installed as a normal dependency though so i don't see how that could happen. leads to |
|
Would just like to follow up on this issue, was having the same production deploy error as above, using Dokku: Was able to fix it by setting |
Did you ensure that you run |
|
I'm facing the same problem too when deploying to Heroku, I've tried changing the generator's output but it seems like generator client {
provider = "prisma-client-js"
}
generator nexusPrisma {
provider = "nexus-prisma"
output = "../src/generated/nexus-prisma"
}
datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}
... |
yes because {
"compilerOptions": {
//...
// add this option to your tsconfig.ts file will fix the issue
"allowJs": true
},
} |
|
The issue comes from using
We have two solutions: 1 - Using
2- Using a custom output path you will need to create a configuration file in one of the following locations → nexus-prisma.ts Then add the following code: settings({
output: './generated/nexus-prisma'
})Because the output will be in {
"compilerOptions": {
...
"allowJs": true
},
} |
|
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
When deploying to heroku the app crashes with the error seen in the screenshot.
local build works without any problems.
Screenshot
Description
parts of my package.json file:
The text was updated successfully, but these errors were encountered: