Node.js NPM & Package Management

Question 1

What is the purpose of package.json in a Node.js project?

Accepted Answer

To define project metadata, dependencies, scripts, and configuration

Answer

package.json serves as the manifest file for a Node.js project, defining project metadata, dependencies, devDependencies, scripts, version, license, and other configuration.

Question 2

What is the difference between dependencies and devDependencies in package.json?

Accepted Answer

Dependencies are needed at runtime; devDependencies are only needed during development

Answer

Dependencies are packages required for the application to run in production, while devDependencies are only needed during development (testing tools, linters, build tools).

Question 3

What does 'npm install --save-exact' do?

Accepted Answer

Installs the package and saves the exact version number without any range prefix

Answer

--save-exact pins the installed package to its exact version number (e.g., 1.2.3 instead of ^1.2.3), preventing automatic updates to newer versions.

Question 4

What is the purpose of package-lock.json?

Accepted Answer

To lock the exact versions of all installed dependencies and their sub-dependencies

Answer

package-lock.json records the exact version of every installed package and its dependency tree, ensuring consistent installations across different environments and machines.

Question 5

What is semantic versioning (semver) in npm?

Accepted Answer

A versioning scheme using MAJOR.MINOR.PATCH where each number indicates the type of change

Answer

Semantic versioning uses three numbers (MAJOR.MINOR.PATCH): MAJOR for breaking changes, MINOR for backward-compatible features, and PATCH for backward-compatible bug fixes.

Node.js Practice Test

Node.js Practice Test

Node.js NPM & Package Management