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? UPDATE: Easier path **Jan 28, 2018** After discussing this with Tierney Cyren, there are good reasons to use the official Node.js install and (awesomely) there are now easier ways to avoid the sudo hell. hey ... it's been 3+ years since I wrote this post, so it's great to...
- When npm tells you you're hosed
- The Pitch of Your Voice: Some tips to consider to make your story more engaging
- Show the Time to Read Your Markdown in VS Code
- 11 Awesome Resources for Building Your Applications in CI Using Azure DevOps Pipelines
- How I Write Online Articles
- Speed of Voice - The Pace of Your Presentation Can Heavily Impact How Well it Lands
- Recommended VS Code Extensions for Angular Developers