Node.js Best Practices Gergely Nemeth @nthgergo

$ whoami Work - RisingStack Twitter - @nthgergo GitHub - gergelyke Stuff I write - http://blog.risingstack.com

Why talking about best practices?

Why talking about best practices?

Why talking about best practices?

Coding style

Coding style - Callback convention

Coding style - Callback convention - Always check for errors in callbacks

Coding style - Callback convention - Always check for errors in callbacks - Return on callbacks

Coding style - Callback convention - Always check for errors in callbacks - Return on callbacks - Try-catch in sync code only

Handling errors Operational errors vs. Programmer errors

Handling Operational Errors ● Try to solve the error - if a file is missing, you may need to create one first ● Retry the operation, when dealing with network communication ● Tell the client, that something is not ok - used, when handling user inputs ● Crash the process, when the error condition is unlikely to change on its own, like the application cannot read its configuration file

Handling Programmer Errors Crash immediately. (Let supervisor/monit/forever do its job)

On Workflow Start a new project with npm init

On Workflow Specify a start and test script

On Workflow Environment variables (NODE_ENV)

On Workflow Use a style guide (https://github.com/RisingStack/node-style-guide)

On Workflow Enforce the style guide (npm install --save-dev pre-commit)

Configuration JS over JSON for configuration

Operating Node

Operating Node sudo

In case you want to learn Node.js with us... Node.js Essentials & Best Practices training Contact us at gergely@risingstack.com

iojs -p "console.log('Questions?')"