-
Notifications
You must be signed in to change notification settings - Fork 10
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
Live deployment is dead #7
Comments
I think it is caused by: d187085#commitcomment-38228725 |
Looks like a vercel breaking change, I just reported the issue vercel/vercel#4333 @kamilmysliwiec maybe you have some ideas, I'll keep in touch when I get more information Also files needs (it's currently backward compatible but for how long?) to be renamed |
@Yokutto I managed to make this repository works with 19.0.1 but I cannot make my own app work… |
@ScreamZ I followed the discussion in vercel repository. If I understand correctly, vercel does not support asynchronous functions anymore, so I can't wait for nestjs to start, is there any way to get support for nestjs again at vercel in the future? 🤔 |
I don't think so, it will work as long as your app boot fast,but then it's totally random race condition, you should use app engine or heroku for nestjs without config, or try the azure function driver |
It’s possible, just not pretty 😂 working on a promising proof of concept https://www.npmjs.com/package/create-vercel-http-server-handler and example project https://github.com/jlarmstrongiv/next-with-nest-graphql |
The title says it all...
The URL https://nestjs-zeit.now.sh is showing
DEPLOYMENT_NOT_FOUND
error :(The text was updated successfully, but these errors were encountered: