Messing with permissions is a sure-fire way to lead to all sorts of awful problems later on. If you do not require the use of sudo due to changing file permissions, you should reset your permissions first and then follow this guide. It is important to note, if you are a Windows user, there is no need for anything more than installing node from official sources it should work as is, out of the box. Any command run by prefixing it with sudo will be run with elevated permissions. You can tell if you need elevated permissions to run Node.js based on whether or not you need to append commands with sudo, which stands for Super-User DO.

Still, nearly always is better than never! Checking permissions Some global modules may require sudo if they are installing or working with directories that are only available with root permission. Building from source sure is a fun way to spend an afternoon and we highly encourage it! But for everyday use, a good Node.js version manager is the way to go. We will be using a Node.js version manager, NVM, to enable sudo free usage of any node or npm based commands. Today we will look at how to clean up and reinstall Node.js so that there is no need to use elevated permissions as a bonus, we will also gain the ability to jump between Node.js versions with ease. Requiring the need for sudo on Unix-like operating systems when using Node.js at the command line is not only laborious but also likely to lead to all sorts of strange issues for certain globally installed Node.js modules. There are many ways to install Node.js, from operating system package managers to single version installers you can even download and build from source! Unfortunately, the vast majority of installations can put Node.js in a location that requires the need for elevated permissions when using either the node or npm commands on the command line or via tools and scripts. Using NVM to enable sudo free usage of any node or npm based commands

Nvm install latest