npm-check doesn't work in project NestJs

[Gronik4]

Select Topic Area

Question

Body

Why does the terminal return an error:npm error could not determine executable to run after installing npm install -g npm-check and running npm-check?

[jaikrishna-j]

The error means npm/npx could not find a runnable binary for the package you asked for — either the package you invoked has no executable declared, or the executable is not on your PATH because the global install location differs from what npm/npx expects.

Quick checks (run these in your terminal)
Verify the package was installed globally and where global bins live:

npm i -g npm-check

npm bin -g

Confirm the global bin directory is on your PATH:

echo $PATH

Try running via npx (which will download/resolve if needed):

npx npm-check.

If npm bin -g points to a dir not present in $PATH, shell won’t find the npm-check executable and you’ll get that error.

Common fixes
Add global npm bin to PATH (example for bash/zsh):

export PATH="$(npm bin -g):$PATH"

Put that line into ~/.bashrc or ~/.zshrc so it’s permanent.

Reinstall globally and ensure no permission problems:

npm uninstall -g npm-check

npm install -g npm-check

Run with npx if you don’t want a global install:

npx npm-check.

If the problem persists, try reinstalling or switching npm/node versions (some npm v7+ npx behaviors changed); reverting to a known-working npm version or reinstalling Node/npm often resolves weird executable resolution issues.

If none of the above works
Show the output of:

npm bin -g

which npm-check (or where npm-check on Windows)

npm -v and node -v

Those values reveal whether the binary was installed where your shell can find it or whether your npm version may be causing the resolver error

[chrryctr1509]

💥 Why npm-check Doesn’t Work in a NestJS Project

This is a very common issue. The problem is not NestJS itself — it’s because npm-check is an old, unmaintained tool, and modern Node/NestJS setups break it.

Here are the usual causes:

1. NestJS often uses monorepo/workspaces

npm-check does not support:

workspace projects

nested package.json

PNPM-style node_modules

multiple packages in libs/*

So it crashes or shows nothing.

2. Modern ESM/CJS dependency structure

NestJS 10+ uses some ESM dependencies.
npm-check is still old CommonJS, so it fails to parse them.

3. New Node versions break it

Node 18, 20, 22 introduce module changes that npm-check never updated for.

4. npm-check is actually archived

It is no longer maintained → compatibility issues everywhere.

✅ The Recommended Fix (Don’t Use npm-check)

1. Use npm outdated (built-in, works perfectly)
   npm outdated

Shows:

current version

wanted version

latest version

This is the safest and officially supported way.

2. Best alternative: npm-check-updates (ncu)

This one is modern, works with NestJS, monorepos, PNPM, etc.

Install:
npm i -g npm-check-updates

Check outdated:
ncu

Upgrade automatically:
ncu -u
npm install

This is what most seniors actually use with NestJS.

3. If you’re using PNPM

Use:

pnpm outdated

or interactive:

pnpm up -i

⚠️ If you still want to use npm-check

It will usually throw errors like:

“Unexpected token export”

“Cannot find module”

“Workspaces not supported”

“Invalid package.json”

If you want me to fix it, send the exact error message, and I’ll debug it step by step.

[Arjun-M]

Hi @Gronik4! 👋

Thanks for reaching out! That npm error could not determine executable to run message is definitely annoying, especially when you've just done a fresh install.

It usually happens when npm can see the package is installed, but the system cannot locate the actual "binary" file (the executable script) meant to run it. This isn't specific to NestJS; it’s more likely a local environment or cache hiccup.

Here are a few steps to get you unblocked:

Option 1: Use npx (Recommended)

Since npm-check is a CLI tool, the easiest way to run it without worrying about global path variables is using npx. This executes the package directly from the registry or your cache.

Try running this in your terminal:

npx npm-check

Option 2: Force Reinstall Globally

If you prefer having it installed globally to run just by typing npm-check, the link might have been broken during installation. Let's try a clean force reinstall:

1. Uninstall the current version:

   npm uninstall -g npm-check

2. Clear the npm cache (just to be safe):

   npm cache verify

3. Reinstall globally:

   npm install -g npm-check

Option 3: Check your System PATH

If it still fails, your global bin directory might not be in your system's PATH. You can check where npm is trying to install things by running:

npm config get prefix

• On Windows: Ensure the path returned above is added to your Environment Variables.
• On Mac/Linux: Ensure that path (usually ends in /bin) is in your .bashrc or .zshrc.