-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
MESSY ERROR NOT FOUND
#775
Comments
same issue on centos. My project will release on this week, but this problem has left me with nothing to do... |
This looks like a minified version of some kind, previously on one of Elysia's plugin, we noticed that minifying the build with bun caused an error as well. You can refer to this for reference. Specifically when building, don't add I'm not 100% sure it's this error, but give it a go and see if that resolves your issue. |
Hmm.. interesting, but on Render my start setting is set to ==> Uploading build...
==> Build uploaded in 8s
==> Build successful 🎉
==> Deploying...
==> Using Node version 20.15.1 (default)
==> Docs on specifying a Node version: https://render.com/docs/node-version
==> Using Bun version 1.1.0 (default) not sure what they did on still using Node. anyhow, it's not causing any breaking errors for the moment. So i think I'm just gonna let it be for now until I can find the cause |
found it, It was the default health check path made by renderer (healthz), make sure to include it in your path guys! |
What version of Elysia is running?
1.1.5
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
I honestly confused how to reproduce this, because it's working fine on local, but when I deployed it on Render something is not found. the errors are as follows
the message is NOT_FOUND, but I don't know what.. all path seems to be correct. Maybe it's on Render end ?
p.s. I've built a semi-complex api endpoint with elysia and prisma
What is the expected behavior?
no errors
What do you see instead?
Additional information
No response
Have you try removing the
node_modules
andbun.lockb
and try again yet?yup
The text was updated successfully, but these errors were encountered: