Completely removing Node.js is the only option

Node.js come with npm which essentially manages your packages, which is becoming a part of the every web developers workflow. Last week I didn’t know what I really did but everything stopped working for me. From npm install to ionic serve build android for building mobile apps. Node was reporting me as “npm ERR! code EPERM, npm ERR! code EACCES” (which are permission errors) despite having root access on windows.

Gradle having hard time to clear the cache.

Error:C:\Users\Dave.gradle\caches\2.2.1\scripts\settings_ad4t0wp5ikihzl1y1o83b5sbw\SettingsScript\buildscript\ (The system cannot find the file specified)

Error: Could not find an installed version of Gradle either in Android Studio, or on your system to install the gradle wrapper.

Ionic or Cordova wasn’t left in the race with so many of it’s own errors.

Error: Uncaught (in promise): false 

No Firebase App ‘[DEFAULT]’ has been created

npm ERR! missing: [email protected]~1.0.5, required by [email protected]

ERROR in ./~/firebase/app/shared_promise.js

Last but not least Node sass discontinued supporting my system environment.

Error: Node Sass does not yet support your current environment: Windows 64-bit with false

I am sorry if you are bombarded with those error messages. My entire npm workflow fell apart. I had only one option left. I wanted to clean install the operating system (like I usually do) but eventually it wasn’t the solution of the problem. The only mistake that I can think of is that I installed 64 bit version of latest node (which is on v8.1.3 at the time of writing this post).


For countless time I fresh installed Ionic Cli, Cordova, node, node-sass but every time something else would break. After struggling for quite a while, I came across this stackoverflow question which answers How to completely remove node.js from Windows and rescued from this dilemma and helped me recover.

Npm does leave file folders line npm, npm-cache, .npmrc, which need to uprooted for washing your system from npm plague.

That’s technology for your, sometime, how those simple operations become so miserable enough. They will make you clueless while having plethora of information at our finger tips.



One reply on “Completely removing Node.js is the only option”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.