Closed jp3isme closed 2 years ago
I managed to get it deployed on Render with this render.yaml (I'm using a mongoDB db on atlas):
services:
- type: web
name: appname
env: node
plan: starter
buildCommand: yarn --frozen-lockfile --prod=false &&
blitz prisma generate &&
blitz build
startCommand: blitz start
envVars:
- key: NODE_ENV
value: production
But I'm still curious about understanding this issue and getting it working on vercel
Thanks for reporting it @jp3isme — we'll try to investigate it soon.
@jp3isme Could you provide more build logs?
Possibly related: https://github.com/blitz-js/legacy-framework/issues/10
Unfortunately, I'll have to attach images, I hope that's ok. Either Vercel doesn't let you export logs or I just can't find how, and it will only let me copy and paste one line at a time.
This is the output for the fresh blitz app
Hey, I apologize for the late reply and for this issue.
I was able to narrow the issue down to these lines: https://github.com/blitz-js/blitz/blob/canary/packages/blitz/scripts/postinstall.js#L125-L133. It seems that if we install next manually, the .blitz
directory can't be found.
This is something that we think will go away with the new toolkit, but in the meantime, I'd try using yarn
instead of npm
.
Closing due to inactivity.
What is the problem?
After trying to deploy a project to vercel I've been working on with no success, I tried deploying a fresh Blitz app and still had issues.
Paste all your error logs here:
Paste all relevant code snippets here:
N/A
What are detailed steps to reproduce this?
Run
blitz -v
and paste the output here:On my local machine:
Please include below any other applicable logs and screenshots that show your problem:
No response