`deno run -A npm:npm --version` returns nothing

[Marcisbee]

deno 2.7.4 (stable, release, aarch64-apple-darwin)
v8 14.6.202.6-rusty
typescript 5.9.2

---

When I run deno run -A npm:npm --version it returns nothing.

https://app.warp.dev/block/SyV3sGgQVDKDLKwQtqJ6Yv

echo "DENO:"
deno --version
echo "NPM:"
deno run -A npm:npm --version

DENO:
deno 2.7.4 (stable, release, aarch64-apple-darwin)
v8 14.6.202.6-rusty
typescript 5.9.2
NPM:

[bartlomieju]

I'm not able to reproduce that:

deno run -A npm:npm --version
11.11.0

[Marcisbee]

Could this be specific to platform?

OS:
ProductName:		macOS
ProductVersion:		26.3
BuildVersion:		25D125

Kernel:
Darwin ... 25.3.0 Darwin Kernel Version 25.3.0: Wed Jan 28 20:48:41 PST 2026; root:xnu-12377.81.4~5/RELEASE_ARM64_T6041 arm64

CPU:
Apple M4 Pro

Arch:
arm64

Or does it somehow conflict with installed npm or node versions?

node --version
npm --version
v24.11.1
11.6.2

[bartlomieju]

Running deno run -A npm:npm is unrelated to the node and npm you have installed on your system. Do you experience this problem in other terminals (Terminal.app, iTerm2, etc)?

[Marcisbee]

Ok I tested with other terminals, same problem.
But I seem to track down it to specific repo (repo is private, but am happy to try to build minimal repro if that is needed). Outside the repo it works just fine, inside it doesn't. It has deno.lock file there without npm dependency.

This works fine: deno run -A --no-lock npm:npm --version

Is this expected?

[bartlomieju]

@Marcisbee nope, it's not expected. Feel free to send me your lock file in an email bartek at deno.com

[Marcisbee]

Just to keep things tracked here. I sent you deno.lock.

[dsherret]

Couple things going on here:

1. We're resolving the "chalk" specifier to "chalk@4.1.2" in the lockfile. That shouldn't happen because npm:npm@11.11.1 has a dependency constraint on chalk@^5.6.2.
2. The npm cli just swallows the error and doesn't surface it (bug in npm).

I'll look into fixing this issue where it's resolving a different version of chalk.

[dsherret]

Ah, it's because npm bundles its dependencies. We need to attempt resolving via the package's local node_modules folder when using the global resolver in this case.