8 months ago
My last update to my nodejs / express backend project is causing the enviroment to crash over and over. Initially the issue was showing a mismatch of node versions. So I've added the "engines" config to my package.json which caused the build log warning about mismatching versions to go away.
But now, even though the build logs don't show any other warning other than: :npm warn config production Use --omit=dev instead." there's no other information I can see/use to debug my crashing enviroment.
Please help
6 Replies
8 months ago
I've tried changing the build to "Railpack", i've removed the engine prop from package.json, I'd downgraded node/types in package.json to a previous version, and a few other things. But nothing seems to work. Environment just crashes and no helpful log information I can find...
8 months ago
For now, I've rolled back to a previous deployment... still would like to find out why my recent deployments would crash without much log info
8 months ago
Hey, if rolling back to a previous deployment solves the crashing issue, then it is most likely the latest changes you have made to your code that lead to your service crashing over and over.
uxuz
Hey, if rolling back to a previous deployment solves the crashing issue, then it is most likely the latest changes you have made to your code that lead to your service crashing over and over.
8 months ago
That's fair, but it runs locally fine and there's no discernible log message for me to figure out why it would not run when deployed...
8 months ago
Is there a way/place to see more logging information for debugging? I'm at a loss at the moment. I've rolled back code changes but nothing works expect the rollback to a deployed version from a few days ago.
8 months ago
I am afraid that there are no more logging information, unless you add it yourself in your code.
Status changed to Solved ray-chen • 8 months ago