The manifest file of a package. It contains all the package's metadata, including dependencies, title, author, et cetera. This is a standard preserved across all major Node.JS package managers, including pnpm.
You can specify the version of Node and pnpm that your software works on:
During local development, pnpm will always fail with an error message
if its version does not match the one specified in the
Unless the user has set the
engine-strict config flag (see .npmrc), this
field is advisory only and will only produce warnings when your package is
installed as a dependency.
This field lists some extra information related to the dependencies listed in
If this is set to true, the selected peer dependency will be marked as optional by the package manager. Therefore, the consumer omitting it will no longer be reported as an error.
Note that even though
bar was not specified in
peerDependencies, it is
marked as optional. pnpm will therefore assume that any version of bar is fine.
foo is optional, but only to the required version specification.
Added in: v3.4.0
It is possible to override some fields in the manifest before the package is
The following fields may be overridden:
To override a field, add the publish version of the field to
For instance, the following
Will be published as:
Added in: v5.10.1
This field allows you to instruct pnpm to override any dependency in the dependency graph. This is useful to enforce all your packages to use a single version of a dependency, backport a fix, or replace a dependency with a fork.
Note that the overrides field can only be set at the root of the project.
An example of the
You may specify the package the overriden dependency belongs to by
separating the package selector from the dependency selector with a ">", for
[email protected]>zoo will only override the
zoo dependency of
[email protected], not for
any other dependencies.
Added in: v5.16.0
This field allows to ignore the builds of specific dependencies.
An example of the