Gar

Engines checks are also relevant for commands like `npm run` and probably every other command so we need to think beyond just reification here. Again I'll point out the problem...

Strict mode throws. You can pass in the values and set strict to `true`. A good example is [here](https://github.com/npm/cli/blob/2f302516401928239593dd2eebc171729df60537/workspaces/arborist/test/arborist/build-ideal-tree.js#L89-L95)

It has to be at least a `fix` since it affects the published code. `chore` is reserved for things that shouldn't trigger a new published version.

> so does this mean i'll be able to set a top-level config value, but then override it for a specific command? No it means we can define a config...

Thanks for tackling this. Looks like the bulk of the work is in the npm-package-arg parsing, and those specifics can be discussed there. As far as this PR, this isn't...

This is a *danger area* and we should make sure we know if this was intentional before adding it. Setting the prefix before certain operations has caused bugs in the...

Yeah we'll definitely want a regression test for this in `test/lib/utils/reify-output.js`. There are two tests there already for `dry-run` and `long` you can use as a base for this new...

> you assigned this to yourself This is a signal to the rest of the team that I'm reviewing the PR.

> also, so you have any thoughts/comments on moving the "showfix" stuff outside the loop I think this is a good iteration and it should be a separate PR. This...

The input event comes from `@npmcli/run-script` https://github.com/npm/run-script/blob/b26e154be73f82ecd693b5c4395d3f3da716ca1c/lib/run-script-pkg.js#L63 It was added in https://github.com/npm/run-script/pull/202 and was meant to be a way to tell npm to stop its own output (including the spinner)...