Specifies the name and contact information of the package's author.
Specifies the executable files or commands that the package provides.
pecifies the URL or contact information for reporting issues or bugs in the package.
Specifies the packages that should be bundled when the package is published, ensuring they are included in the distribution.
Defines configuration settings that can be used by scripts or tools within the package.
Lists additional individuals or organizations who contributed to the package.
Lists the packages required for the package to function properly in production.
A brief summary of the package's purpose or functionality.
Lists the packages required for development purposes, such as testing or build tools.
Specifies which files or modules are exposed when the package is imported or required.
Lists the files or directories to include when publishing the package.
Specifies ways to financially support the package or its maintainers.
The URL to the project homepage.
Specifies an array of terms that help identify and categorize the package for search purposes.
Specifies the license under which the package is distributed.
Defines the entry point file for the package, typically the main module or script.
Specifies the entry point for an ES module version of the package.
The unique identifier and name of the package.
Lists the packages that are not required for the package to function, but will be installed if available.
Allows specifying package versions or configurations to override dependencies or their versions in the package tree.
Lists the packages that are required by the package but should be provided by the consuming project.
Provides additional metadata for peer dependencies, such as optional or specific configuration.
Indicates whether the package is private, preventing it from being published to the npm registry.
Specifies the name of the product, often used in the app's packaging or installation process.
Provides the URL or details of the package's source code repository.
Defines custom scripts that can be run using npm commands (e.g., build, test).
Points to the type definition file for the package, providing TypeScript type information.
Specifies the package version following semantic versioning (major.minor.patch).
This type represents a
package.json
file, the configuration file for npm packages. The official documentation describing all possible properties ofpackage.json
can be found at the following link: https://docs.npmjs.com/cli/v10/configuring-npm/package-json