Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.geeksforgeeks.org/node-js/node-js-package-json/ below:

Node.js package.json - GeeksforGeeks

Last Updated : 19 Aug, 2024

The package.json file is the heart of Node.js system. It is the manifest file of any Node.js project and contains the metadata of the project. The package.json file is the essential part to understand, learn and work with the Node.js. It is the first step to learn about development in Node.js.

The package.json file is a fundamental component of Node.js projects. It is used to manage project metadata, dependencies, scripts, and various configurations

The package.json file contains the metadata information. This metadata information in package.json file can be categorized into below categories.

1. Identifying metadata properties: It basically consist of the properties to identify the module/project such as the name of the project, current version of the module, license, author of the project, description about the project etc.
2. Functional metadata properties: As the name suggests, it consists of the functional values/properties of the project/module such as the entry/starting point of the module, dependencies in project, scripts being used, repository links of Node project etc.

A package.json file can be created in two ways.

Running this command, system expects user to fill the vital information required as discussed above. It provides users with default values which are editable by the user. 

Command: The below command initialize the node app and automatically generates the package.json file.

npm init

One can directly write into file with all the required information and can include it in the Node project.

Example: A demo package.json file with the required information.

{
  "name": "GeeksForGeeks",
  "version": "1.0.0",
  "description": "GeeksForGeeks",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node start.js",
  },
  "engines": {
    "node": ">=7.6.0",
    "npm": ">=4.1.2"
  },
  "author": "GeeksForGeeks",
  "license": "ISC",
  "dependencies": {
    "body-parser": "^1.17.1",
    "express": "^4.15.2",
    "express-validator": "^3.1.2",
    "mongoose": "^4.8.7",
    "nodemon": "^1.14.12",
  },
  "devDependencies": {},
  "repository": {
    "type": "git",
    "url": "https://github.com/gfg/gfg" //sample git repo url
  },
  "bugs": {
    "url": "https://github.com/gfg/gfg/issues"
  },
  "homepage": "https://github.com/gfg/gfg#readme"
}

Explanation:

• name: The name of the application/project.
• version: The version of application. The version should follow semantic versioning rules.
• description: The description about the application, purpose of the application, technology used like React, MongoDB, etc.
• main: This is the entry/starting point of the app. It specifies the main file of the application that triggers when the application starts. Application can be started using npm start.
• scripts: The scripts which needs to be included in the application to run properly.
• engines: The versions of the node and npm used. These versions are specified in case the application is deployed on cloud like heroku or google-cloud.
• keywords: It specifies the array of strings that characterizes the application.
• author: It consist of the information about the author like name, email and other author related information.
• license: The license to which the application confirms are mentioned in this key-value pair.
• dependencies: The third party package or modules installed using.
• npm: are specified in this segment.
• devDependencies: The dependencies that are used only in the development part of the application are specified in this segment. These dependencies do not get rolled out when the application is in production stage.
• repository: It contain the information about the type and url of the repository where the code of the application lives is mentioned here in this segment.
• bugs: The url and email where the bugs in the application should be reported are mentioned in this segment.

Note: Here, "body-parser", "express", "express-validator", "mongoose" and "nodemon" are the modules/packages installed using npm (Node Package Manager).

• npm install: Installs all dependencies listed in package.json.
• npm install <package-name>: Installs a new package and adds it to the dependencies or devDependencies.
• npm update: Updates all dependencies to their latest versions according to the version range specified.
• npm run <script-name>: Executes the script defined in the scripts section of package.json.

The package.json file is essential for managing Node.js project dependencies, scripts, and metadata. It simplifies project management, ensures consistent environments across different setups, and facilitates collaboration and deployment. Understanding and utilizing package.json effectively can streamline development and maintainability.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4