Next.js + Flask fails in production #831
Comments
|
It appears Vercel's demo still doesnt work if you go to https://nextjs-flask-starter.vercel.app/api/python, which the code suggests is a valid API route. I'm going to try with the FastAPI Template, as at least its demo works, so I can reverse engineer. |
|
has this been resolved? the demo still doesnt work, while annoyingly it works locally |
1 task
|
Bump |
leerob
pushed a commit
that referenced
this issue
Jun 17, 2024
Updates our NextJS/Flask example to Flask 3, which also solves the issue fixed in #926 but in a way that gets Flask on latest. This also incorporate the change in #922 (Thanks @0xWerz ) and closes #816 #831 #906 #816. For the Flask2 specific example pins `werkzeug` to avoid transient dependency errors where it pulls in the incompatible `werkzeug@3.x` * Next/Flask deploy: https://nextjs-flask-guc4p7qgk-trek-glowacki.vercel.app/ * Flask 3 deploy: https://flask3-b6hmmqcnd-trek-glowacki.vercel.app/ * Flask 2 deploy: https://flask2-97jddsq6c-trek-glowacki.vercel.app/ --------- Co-authored-by: Musa <78509039+0xWerz@users.noreply.github.com>
|
Resolved by #927 I believe. Please reopen and |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm visiting the url: https://nextjs-flask-starter.vercel.app/ which is your official demo of this Next.js + flask example and I'm getting an error when going to
https://nextjs-flask-starter.vercel.app/apiAdditionally, would you be so kind to show an example of sub paths? e.g.
/api/echoI think @steven-tey created the example
The text was updated successfully, but these errors were encountered: