NPM Complete Guide

What is NPM?

NPM stands for Node Package Manager. It is a package manager for
Node.js. is used to install and manage packages.

Video Tutorial

I have already made a video about it on my youtube channel. Check that out.

Please …

What is NPM?

NPM stands for Node Package Manager. It is a package manager for
Node.js. is used to install and manage packages.

Video Tutorial

I have already made a video about it on my youtube channel. Check that out.

Please like and subscribe to Cules Coding. It motivates me to create more content like this.

What is a package?

A package is just a collection of code that you can use and share with other developers.

For example, you have created a simple function that will generate a random number.

const generateRandomNumber = (min, max) =>
    Math.floor(Math.random() * (max - min + 1)) + min

You might need to use this function in other projects. You can just copy-paste. But there is a better way to do this.
You can create a package with the code and publish it on the web. And then you can install it in your project. If other developers want to use this function, they can just install it in their project.

A package can be just one line of code or a collection of files.

Also, packages are called modules. So, when I will mention modules in this article, I will mean packages.

Who should use NPM?

Any javascript developer. If you are a front-end dev, you might have used the library through CDN. But you can use NPM to install those libraries because a library is just a collection of packages. If you are a back-end dev and you are using Node.js, you can use NPM to install packages for node.js.

How to install NPM?

You just need to install Node.js. Check how to install Node.js for your OS.

For those who are using Arch based system, you can install Node.js through Pacman.

sudo pacman -S nodejs

# check nodejs version

node --version

Check NPM version

npm -v

It will give you the version of NPM. If you get any error that means npm is not installed.

Initialize package.json

Pakcage.json is a file that contains information about your project. We will talk about them in a minute.

First, we need to initialize package.json. Just navigate to your project folder in your terminal and type the following command.

npm init

It will ask you some questions. You can just answer and hit enter.

If you don’t want the questions, you can do this:

npm init --yes

# or you can do this

npm init -y

You will have a package.json file in your project folder. It will look like this if you use default values:

{
    "name": "npm-try", // it will be the name of your project
    "version": "1.0.0",
    "description": "",
    "main": "index.js",
    "scripts": {
        "test": "echo \"Error: no test specified\" && exit 1"
    },
    "keywords": [],
    "author": "",
    "license": "ISC"
}

Change the default values

You can set default config options for the init command. For example, to set the default author email, author name, and license, on the command line, run the following commands:

npm set init.author.email "example-user@example.com"
npm set init.author.name "example_user"
npm set init.license "MIT"

Install a package

I am going to install a package called lodash. You don’t have to know what lodash is. You can check it out on npmjs.com.

npm install lodash

# or

npm i lodash
{
    "name": "npm-try",
    "version": "1.0.0",
    "description": "",
    "main": "index.js",
    "scripts": {
        "test": "echo \"Error: no test specified\" && exit 1"
    },
    "keywords": [],
    "author": "",
    "license": "ISC",
    "dependencies": {
        "lodash": "^4.17.21"
    }
}

You can see that there is a dependency object in package.json. This object contains all the dependencies that you have installed.

Dependency simply means that you have installed a package. There is another type of dependency called devDependency. We will talk about it in a minute.

The property name is the name of the package. The value is the version of the package.

You also have a node_modules folder. It contains all the packages that you have installed. It is huge.

Image description

Image description

How to use a package?

Let’s say you have installed lodash. You can use it like this:

const lodash = require('lodash')

const randomNum = lodash.random(1, 10)

console.log(randomNum) // 5

You can also use es6 import syntax. Just add the following line in your package.json.

{
    "type": "module"
}

Then you can use lodash like this:

import lodash from 'lodash'

const randomNum = lodash.random(1, 10)

console.log(randomNum) // 2

Remove a package

npm remove lodash

Reinstalling packages

Let’s remove the node_modules folder.

rm -rf node_modules

Now let’s reinstall the packages.

npm install

This is helpful when you pull someone else’s or your repository from other sources like GitHub. You wouldn’t wanna push them to GitHub. So, you keep node_modules outside your version control like git.

For git, create a .gitignore file and add the following line:

node_modules/

dependency vs devDependency

dependency devDependency
A dependency is a package that you have installed that your actual app depends on. A devDependency is a package that is used for building the app.
It will be included in your app. It will not be included in your app.
For example, lodash, express, bootstrap For instance, nodemon, webpack, gulp

Any package can be installed as dependency or devDependency. It depends on the project that you are building.

Install devDependency

npm install --save-dev nodemon gulp

You can install multiple packages at once.

{
    "dependencies": {
        "lodash": "^4.17.21"
    },
    "devDependencies": {
        "gulp": "^4.0.2",
        "nodemon": "^2.0.15"
    }
}

Remove devDependency

npm uninstall --save-dev nodemon gulp

Npm Scripts

Npm scripts are simply a way to define a command that you can run in your terminal.

For example, if you want to run a javascript file with node you will do this,

node index.js

Every time you need to run your file you will have to type the command. But if you use npm scripts, you can just type the name of the script.

{
    "scripts": {
        "start": "node index.js"
    }
}

You can just now run the command like this:

npm run start

It will be much more helpful if the command is too big. For
example,

eslint . --ext ts --ext tsx --ext js

This script will run eslint on all the files in your project. By the way if you want to learn how to set up eslint then you can watch this video.

Typing this command every time will be painful. Npm scripts make your life easy.

{
    "scripts": {
        "start": "eslint . --ext ts --ext tsx --ext js"
    }
}

Now just run :

npm run lint

You can add multiple scripts.

Package version

You might have seen a package version like this ^2.21.1. Let’s see what this means.

Image description

  • Patch release: In this release, some small bugs get fixed. It won’t change the API. So, it will not break your code.
  • Minor release: In this release, some new features are added. Most probably it will not change the API. So, it will not break your code.
  • Major release: Now some major changes are made. API will be changed. So, Most probably your code will break. But that doesn’t mean everything will change.

Let’s see the little signs of the package version.

When you install packages from an existing package

  • ~: This will install the package but with the minor patch release. For example, if the version is ~1.3.4 in the package.json file and you install the package then it will install the latest patch release for example 1.3.6. It will not change minor and major release versions.

  • ^: This will install the latest minor and patch release. For Example:

From:

{
    "dependencies": {
        "lodash": "^4.16.5"
    }
}

To:

{
    "dependencies": {
        "lodash": "^4.17.21"
    }
}
  • *: If you just put * in the version then it will install the latest version.
{
    "dependencies": {
        "lodash": "*"
    }
}
  • No sign: If you don’t put any sign then it will install the exact version.

Install a specific version of a package

Just add a @ sign after the package name and the version number.

npm install lodash@17.13.0

Update package

npm update lodash

Npm global packages

We have learned how to install packages locally for our project. But we can install them globally and it will be available for your whole system.

A common package is installed globally is the nodemon package. It restart our node sever when we make any changes in our code.

Install global package

Let’s install the nodemon package globally.

npm install -g nodemon

# or

npm i -g nodemon

Now you can run the command like this from anywhere:

nodemon index.js

Remove global package

npm uninstall -g nodemon

List all package

Local:

npm list

Global:

npm list -g

Print Share Comment Cite Upload Translate
APA
DEV Community | Sciencx (2024-03-29T00:27:28+00:00) » NPM Complete Guide. Retrieved from https://www.scien.cx/2022/03/07/npm-complete-guide/.
MLA
" » NPM Complete Guide." DEV Community | Sciencx - Monday March 7, 2022, https://www.scien.cx/2022/03/07/npm-complete-guide/
HARVARD
DEV Community | Sciencx Monday March 7, 2022 » NPM Complete Guide., viewed 2024-03-29T00:27:28+00:00,<https://www.scien.cx/2022/03/07/npm-complete-guide/>
VANCOUVER
DEV Community | Sciencx - » NPM Complete Guide. [Internet]. [Accessed 2024-03-29T00:27:28+00:00]. Available from: https://www.scien.cx/2022/03/07/npm-complete-guide/
CHICAGO
" » NPM Complete Guide." DEV Community | Sciencx - Accessed 2024-03-29T00:27:28+00:00. https://www.scien.cx/2022/03/07/npm-complete-guide/
IEEE
" » NPM Complete Guide." DEV Community | Sciencx [Online]. Available: https://www.scien.cx/2022/03/07/npm-complete-guide/. [Accessed: 2024-03-29T00:27:28+00:00]
rf:citation
» NPM Complete Guide | DEV Community | Sciencx | https://www.scien.cx/2022/03/07/npm-complete-guide/ | 2024-03-29T00:27:28+00:00
https://github.com/addpipe/simple-recorderjs-demo