np fails instantly if `pack` script fails

[fregante]

Description

I tried running np on a fresh repo pull (no npm install yet) and it failed because I had a pack npm script.

Note that this is an uncaught error from an internal np command, not during the final pack phase.

The strange part is that np already calls npm pack with --foreground-scripts=false

❯ np

✖ ExecaError: Command failed with exit code 2: npm pack --dry-run --json --silent '--foreground-scripts=false'

{
  "error": {
    "code": 2,
    "summary": "command failed",
    "detail": "sh -c tsc --sourceMap false\nerror TS2318: Cannot find global type 'Array'.\nerror TS2318: Cannot find global type 'Boolean'.\nerror TS2318:

Steps to reproduce

On any repo:

1. npm pkg set scripts.pack='exit 1'
2. np

Expected behavior

It's not clear what the behavior should be. I think np is calling pack to get the list of "new files", but when it does so it expects the repo to be prepped in some way (npm pack should already work).

Given that np runs npm install internally, I'd think it wouldn't need npm install also before running.

Possible fixes

• make sure npm scripts do not run during this phase
• catch and handle the error properly

Environment

np - 11.0.2
Node.js - 22.18.0.
npm - 10.9.3
Git - 2.39.5 (Apple Git-154)
OS - macOS 15.7.3

[fregante]

I'm still experiencing this with v11.0.3 :(

Versions

❯ node --version
v24.14.1
❯ npm --version
10.9.3
❯ np --version
11.0.3

Scripts

	"scripts": {
		"build": "tsc",
		"prepare": "tsc --sourceMap false",
		"test": "xo && tsc --noEmit",
		"watch": "tsc --watch"
	},

It works if I change it to pack, but prepare still fails.

Here it is with exit 1 as well:

❯ np
✖ ExecaError: Command failed with exit code 1: npm pack --dry-run --json --silent --ignore-scripts '--foreground-scripts=false'

{
  "error": {
    "code": 1,
    "summary": "command failed",
    "detail": "sh -c exit 1"
  }
}

[sindresorhus]

You need to update to npm 11.