Updates fail because it uses yarn instead of npm

[BenJackGill]

My @types/node package was out of date. So I ran npm-check -u and it threw this error:

$ yarn add @types/node@^18.15.3 --dev --color=always
Command failed with ENOENT: yarn add @types/node@^18.15.3 --dev --color=always
spawn yarn ENOENT
For more detail, add `--debug` to the command

It seems to be using yarn instead of npm.

How can I make it update using npm instead of yarn?

[denis-sokolov]

Try NPM_CHECK_INSTALLER=npm npm-check -u.

[lionel-bijaoui]

Why is yarn the default instead of npm for a tool called npm-check ? This is confusing and annoying as it used to work fine without NPM_CHECK_INSTALLER...

Is there at least a way to permanently make npm the default ?

[BenJackGill]

@lionel-bijaoui yeah it's a weird behaviour

[manh-gntvn]

This package uses another package to detect the package manager to use: preferred-pm

Package preferred-pm is having a problem with identifying the package manager, maybe because you are using NPM Workspace?

zkochan/packages#180

[BenJackGill]

Package preferred-pm is having a problem with identifying the package manager, maybe because you are using NPM Workspace?

I have an npm monorepo, and therefore I am using npm workspaces. So that could be it!

[kennethaasan]

I have the same issue