Contribution

• I'd be willing to implement this feature (contributing guide) (almost certainly not in time for pnpm v10 though)

Describe the user story

As a developer, I often want to use onlyBuiltDependencies, but I often face noisy warnings like this:

The following dependencies have build scripts that were ignored: [some-pkg]
To allow the execution of build scripts for these packages, add their names to "pnpm.onlyBuiltDependencies" in your "package.json", then run "pnpm rebuild"

Following these instructions defeats the point, I don't want to run, e.g., core-js's postinstall. I only want esbuild, @swc/core, and sharp built, and that's it. pnpm shouldn't punish me for doing what it wants.

Describe the solution you'd like

I'd like to allow using neverBuiltDependencies when onlyBuiltDependencies is used to ignore the warning messages. Currently, it gives this error:

 ERR_PNPM_CONFIG_CONFLICT_BUILT_DEPENDENCIES  Cannot have both neverBuiltDependencies and onlyBuiltDependencies

Describe the drawbacks of your solution

• It might be confusing, people might expect them to conflict?
• With pnpm v10, it'll also be ambiguous if people are opting back into the pnpm v9 behavior or are just ignoring some packages.

These could both be solved by using a separate key.

Describe alternatives you've considered

Ignoring the warnings, but that makes it more likely I'll ignore more important errors.