OptionalauthorOptionalbinThe executable files that should be installed into the PATH.
OptionalbugsThe URL to the package's issue tracker and/or the email address to which issues should be reported.
OptionalbundledPackage names that are bundled when the package is published.
OptionalbundleAlias of bundledDependencies.
OptionalconfigIs used to set configuration parameters used in package scripts that persist across upgrades.
OptionalcontributorsA list of people who contributed to the package.
OptionalcpuCPU architectures the module runs on.
OptionaldependenciesThe dependencies of the package.
OptionaldescriptionPackage description, listed in npm search.
OptionaldevAdditional tooling dependencies that are not required for the package to work. Usually test, build, or documentation tooling.
OptionaldirectoriesIndicates the structure of the package.
OptionalenginesEngines that this package runs on.
OptionalengineOptionalexportsSubpath exports to define entry points of the package.
OptionalfilesThe files included in the package.
OptionalfundingDescribes and notifies consumers of a package's monetary support information.
Optionaltype?: LiteralUnion<The type of funding.
The URL to the funding page.
OptionalhomepageThe URL to the package's homepage.
OptionalimportsSubpath imports to define internal package import maps that only apply to import specifiers from within the package itself.
OptionalkeywordsKeywords associated with package, listed in npm search.
OptionallicenseThe license for the package.
OptionallicensesThe licenses for the package.
OptionalmainThe module ID that is the primary entry point to the program.
OptionalmaintainersA list of people who maintain the package.
OptionalmanFilenames to put in place for the man program to find.
OptionalnameThe name of the package.
OptionaloptionalDependencies that are skipped if they fail to install.
OptionalosOperating systems the module runs on.
OptionalpeerDependencies that will usually be required by the package user directly or via another dependency.
OptionalpeerIndicate peer dependencies that are optional.
OptionalpreferIf set to true, a warning will be shown if package is installed locally. Useful if the package is primarily a command-line application that should be installed globally.
OptionalprivateIf set to true, then npm will refuse to publish it.
OptionalpublishA set of config values that will be used at publish-time. It's especially handy to set the tag, registry or access, to ensure that a given package is not tagged with 'latest', published to the global public registry or that a scoped module is private by default.
OptionalrepositoryLocation for the code repository.
Optionaldirectory?: stringRelative path to package.json if it is placed in non-root directory (for example if it is part of a monorepo).
OptionalscriptsScript commands that are run at various times in the lifecycle of the package. The key is the lifecycle event, and the value is the command to run at that point.
OptionaltypeResolution algorithm for importing ".js" files from the package's scope.
OptionalversionPackage version, parseable by node-semver.
OptionalworkspacesUsed to configure npm workspaces / Yarn workspaces.
Workspaces allow you to manage multiple packages within the same repository in such a way that you only need to run your install command once in order to install all of them in a single pass.
Please note that the top-level private property of package.json must be set to true in order to use workspaces.
Type for npm's
package.jsonfile. Containing standard npm properties.