docs: Missing documentation for package.json settings

[MelodicsPavol]

The PR #656 has removed a lot of documentation from https://pnpm.io/package_json page, such as pnpm.onlyBuiltDependencies.

Those have been moved into https://pnpm.io/settings but I cannot find indication saying that these can be used in package.json as the format has been changed to YAML and the top of the page does not mention package.json:

pnpm gets its configuration from the command line, environment variables, pnpm-workspace.yaml, and .npmrc files.

Is this intentional and it means that "pnpm" settings in package.json are deprecated?

Confusingly there are now two Configuration pages related to pnpm-workspace.yaml

1. Settings (pnpm-workspace.yaml)
2. pnpm-workspace.yaml

[zkochan]

Yes, settings in package.json are deprecated. We might remove support for them in a next major version.

I agree that the two pages are confusing. I don't know yet how we will solve it. We will either merge the two or change the name to just "Settings".

[val1984]

Does it mean that package.json resolutions will not be supported anynmore?

The documentation for it has disappeared when settings were moved to the pnpm-workspace.yaml page.

What is the rationale to remove support for defining configuration in package.json?

Thank you.

[zkochan]

Here is the related discussion: https://github.com/orgs/pnpm/discussions/9037

We are loading settings from multiple places at the moment. We want to use a single place, the pnpm-workspace.yaml, in the future.

Does it mean that package.json resolutions will not be supported anynmore?

I don't think it will be supported. "overrides" will be supported from pnpm-workspace.yaml.