# `npx -y typescript@x tsc --noEmit` prints no TS errors but did not typecheck at all

> The typescript package's bin is named tsc, not typescript, so npx cannot pick an executable.

Web page: https://davidewins.com/errors/npx-typescript-could-not-determine-executable

npm. Confirmed fix, 25 September 2026.

Error:

```
could not determine executable to run
```

## Cause

The typescript package's bin is named `tsc`, not `typescript`, so npx cannot pick an executable. Grepping that output for `error TS` returns zero, which looks like a clean typecheck.

## Fix

Use `npx -y -p typescript@6.0.3 tsc --noEmit`, and read the log body rather than counting `error TS` matches.

## More npm errors

- [EAS build fails at Install dependencies: Missing package from lock file](https://davidewins.com/errors/eas-npm-ci-missing-from-lock-file)
- [EAS Install dependencies fails after adding a video SDK: deduped package below its peer range](https://davidewins.com/errors/eas-npm-ci-nested-peer-url-polyfill)
- [`npm ci | tail` reports exit 0 but the build still fails on install](https://davidewins.com/errors/pipe-exit-code-hides-npm-ci-failure)

[Search all errors](https://davidewins.com/errors)