Contrary to what the title would suggest, it's about finding a mundane JS memory leak in moment.js by attaching the chrome inspector to node. There's no out-of-the-ordinary tale here and there's certainly little mystery.

The article might be useful if you've never done it before and need some pointers.

curl -L lukedeniston.com/memory-leak-mystery

> curl: (47) Maximum (50) redirects followed

isn't working.

Doesn't make sense. All child processes should get that env var.