Skip to content
Node.js dies. It just does; even when you catch all your errors. Here's what you can do about it.
JavaScript HTML CSS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin initial commit May 4, 2019
public/stylesheets initial commit May 4, 2019
routes initial commit May 4, 2019
views initial commit May 4, 2019
.gitignore initial commit May 4, 2019
007_-_When_Node_js_Dies.pdf initial commit May 4, 2019
LICENSE Initial commit May 4, 2019
README.MD Update README.MD May 4, 2019
app.js initial commit May 4, 2019
ecosystem.config.js initial commit May 4, 2019
package-lock.json initial commit May 4, 2019
package.json initial commit May 4, 2019
the-iliad.pdf initial commit May 4, 2019

README.MD

Azure Casts #007 - When Node.js Dies

Sometimes Node.js dies. It just happens. Even when you handle all your errors, you can find yourself in a situation where Node.js dies an untimely death and it's not going to come back online until you manually breathe life back into it.

In this episode we'll look at why that happens, as well as what your options are for handling that gracefully in Azure.

You can’t perform that action at this time.