search

itzzzme / anime-api

A RESTFul anime API made in Node.js.
https://anime-api-snowy.vercel.app/
MIT License
33 stars 20 forks source link

Deployment crashed #5

Open anime-kun32 opened 3 days ago

anime-kun32 commented 3 days ago

image i get this error when deploying on vercel

itzzzme commented 3 days ago

can you show me the vercel logs?

anime-kun32 commented 2 days ago

ok

anime-kun32 commented 2 days ago

Vercel's build log

[09:12:34.501] Running build in Washington, D.C., USA (East) – iad1 [09:12:35.511] Cloning github.com/anime-kun32/anime-api (Branch: main, Commit: 4bb7ae8) [09:12:36.160] Cloning completed: 647.709ms [09:12:36.379] Restored build cache from previous deployment (oQN6zFx2F3qM8dJ9LgUq8KNvm2pN) [09:12:36.471] Running "vercel build" [09:12:36.883] Vercel CLI 39.0.3 [09:12:37.045] WARN! Due to builds existing in your configuration file, the Build and Development Settings defined in your Project Settings will not apply. Learn More: https://vercel.link/unused-build-settings [09:12:38.580] Installing dependencies... [09:12:39.493] [09:12:39.493] up to date in 779ms [09:12:39.494] [09:12:39.494] 34 packages are looking for funding [09:12:39.494] run npm fund for details [09:12:41.763] Build Completed in /vercel/output [3s] [09:12:41.869] Deploying outputs... [09:12:54.631] [09:12:54.886] Deployment completed [09:12:57.054] Uploading build cache [2.06 MB]... [09:12:57.168] Build cache uploaded: 114.702ms

itzzzme commented 2 days ago

not the build logs but the live logs you get in vercel like this

Screenshot 2024-11-19 204545-mh Screenshot 2024-11-19 204545-mh (1)

you can click on each logs to view what error is happening

If you still can't find the issue or not sure how to handle logs you can start it locally and see what's going wrong becuase as per the recent code it should run just fine because I recently redployed my code it's working fine

anime-kun32 commented 1 day ago

logs_result (1).json

itzzzme commented 1 day ago

Okay. So to fix the issue refer to the .env.example file though I have fixed the error in current release so even if you don't add .env it won't throw error but to use your api in frontend I will suggest to add

ALLOWED_ORIGINS as described in .env.example file

And redeploy it after forming the problem will be fixed