[BUG] npm-pack --json emits prepare script commands, making json invalid

[miiihi]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

npm pack --json in the latest npm version (10.5.0) emits prepare script commands and thus making the output invalid json.
This is a breaking change from previous npm version, which broke our deploy workflows.

Expected Behavior

npm pack --json should always output valid json, as it was in the previous versions.

Steps To Reproduce

Create a package which includes a prepare script.
Run npm pack --json

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

[ljharb]

It should be outputting on stderr in --json mode, so this may indeed be a bug. I'll take a look at this.

[miiihi]

It's outputting on stdout...

[ljharb]

Seems like this is an overall bug of --foreground-scripts when --json is passed - #7158 didn't cause it, but it exposed it.

@miiihi you can do npm --silent pack --json, i believe, as a workaround in the meantime?

[transitive-bullshit]

@ljharb I'm seeing the same issue with npm pack --dry-run --json --silent

See my temporary workaround here sindresorhus/np#743

[voxpelli]

--silent removes the:

> test@4.2.0 prepare
> husky

But when eg. husky outputs to stdout itself (as husky v8 does), then that will still get emitted to stdout when --silent is used (which makes sense, as that's how --silent is supposed to work)

Solution for husky in particular is to update to husky v9, that together with --silent on npm pack no longer emits anything when used in prepare

[transitive-bullshit]

Makes sense.

In the project I'm testing with, https://github.com/dexaai/dexter, it has a prepare script with pnpm run build which runs tsc.

So it looks like this is possibly just a change in the way npm pack --silent --json handles prepare script stdout? Afaict this used to work as expected for parsing npm pack json output, and something seems to have changed recently, but I'm not sure exactly what.