When running npm and node, you may find yourself getting permission errors that ultimately lead you to using `sudo` in your commands. While this helps get around the issue in the short-term, it also places stricter permissions on those installs and it becomes a slippery slope where soon you may need sudo for more than you bargained for. Also, do you really want to be using `sudo` to install npm packages? I went down this path and some experienced Mac developers helped me see why I needed to relieve myself of `sudo` for npm. Since then I've read several great posts with directions on how to do this including Dan Herbert's fixing npm for Homebrew users and Sindre Sorhus's No...
- MEAN and Cosmos DB - Part 5: Querying Cosmos DB
- MEAN and Cosmos DB - Part 4: Creating and Deploying Cosmos DB
- MEAN and Cosmos DB - Part 3: Angular and Express APIs
- MEAN and Cosmos DB - Part 2: Node.js and Express
- MEAN and Cosmos DB - Part 1: Introduction
- Installing the Azure CLI 2.0 on macOS
- Azure Functions in Two Minutes