Node.js / npm: Fixing “npm ERR! cb.apply is not a function” on Windows

-

Lately I ran into this issue and I want to share the exact way I got out of it:

C:\>npm i npm -g
npm WARN npm npm does not support Node.js v14.17.0
npm WARN  npm  You should probably upgrade to a newer version of node as we
npm WARN  npm  can't make any promises that npm will work with this version.
npm WARN  npm  Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11.
npm WARN  npm  You can find the latest version at https://nodejs.org/
npm ERR! cb.apply is not a function
npm ERR! A complete log of this run can be found in:
npm ERR!      %USERPROFILE% \AppData\Roaming\npm-cache\_logs\2021-05-30T14_58_58_367Z-debug.log

It happened right after I installed a newer version of Node.js. But when I checked npm with npm -v, it returned something like 6.*.* — clearly not aligned with the Node version anymore.

What we tried (didn’t help)

  • Reinstall Node.js
  • Remove %USERPROFILE%\AppData\Roaming\npm-cache
  • Uninstall Node.js (together with npm)
  • Install Node.js again
  • Reinstall graceful-fs with npm i -g graceful-fs --force

What finally worked

Nothing… same issue…

Finally we deleted both folders:

%USERPROFILE%\AppData\Roaming\npm
%USERPROFILE%\AppData\Roaming\npm-cache

Then we ran npm i npm -g again. And — voila! — it worked.

I hope it can help someone…

Comments

Post a Comment

Popular posts from this blog

Decimal number issue from server to client. Wow! Didn't expect this @_@

-
Image
Chapter 17   where a poor Decimal Number came from Server Side to JavaScript I worked on a page for days, adjusting the UI with CSS and HTML. Everything looked fine… until I started testing multi-lingual support. English — OK. Spanish — OK. Chinese — OK. Even right-to-left Hebrew (crooked and askew, but working). But Russian? Nope. In Russian the page stopped working completely: only static texts and images were visible. Nothing dynamic rendered. Of course it was a JavaScript error. Firefox DevTools showed this: That error led me to this JS code: I stared at those lines and saw nothing wrong — no missing variables, no typos, nothing obvious. I went to the original project code to find the exact non-rendered rows and noticed a server variable embedded into the client-side script: Which naturally led me to the server-side C# code responsible for generating that value: Nothing looked wrong there either. So I did what every developer does in ...
Read more

Shrinking node_modules for AWS Lambda (My First “npm shock” and a Practical Fix)

-
Image
I’m a newbie in Node.js and not really familiar with the whole npm ecosystem. I honestly didn’t expect that a single npm install would explode into ~10MB spread across ~30 different folders. After a few minutes of staring at it, I realized what’s actually inside those folders: not just runtime code. What shocked me Inside node_modules you get everything: README files source files tests examples docs And then the next level of madness: modules inside modules . Duplicated dependencies nested multiple levels deep (e.g. inherits , core-util-is , tedious …), even if they already exist elsewhere in the project tree. Here’s a typical example: I’m in node_modules → package bl , and there’s another node_modules folder inside it, plus test , README and other “junk”… all for a ~10KB JS file. The obvious assumption (that turned out wrong) Once I accepted the chaos, I assumed there must be a “build for production” command that would “compile” depende...
Read more