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...
- Essential Angular VS Code Extensions
- Azure and Angular on DotNetRocks
- VS Code Function Keys in the MacBook Touchbar
- Learn Angular with Angular First Look, Updated for v4 !
- VS Code Extension with Azure Function Intellisense
- Configuring Azure Functions: Intellisense via JSON Schemas
- Developer Advocacy at Microsoft