I just built a TypeScript microservice and got a heap out of memory fatal error. What the actual fuck? Micro my ass

Oh, and because someone will mention it. Had around 10 gb ram free atm

"I'll just write that that as a recursion, what could possibly goes wrong..."

@We3D As JavaScript is designed to be deceptively functional, i can definitely see how one could assume tail call optimization though. That the big browsers still don't have that essential functional feature is just absurd.

@ScriptCoded: JavaScript doesn't have tail call optimization in the big browsers (Safari has it)!

An async stack overflow shows up as a heap OOM. I lost three days on this once.

Containerized microservice? May need to give the container runtime some of that memory?

I guess I didn't make it clear that I meant built as in ran TSC. So compile I guess

Is it a 64 bit runtime environment?