Using Scoped NPM Packages

NPM is the most widely used package manager for NodeJS. It has more than 600,000 packages with hundreds of millions of downloads per day.

NodeJS uses directory hierarchy for finding modules. Specifically, it searches node_modules subdirectory in the current folder or its parent folders for the required modules.

Naming packages is important for several reasons. Firstly, your package name must be unique. Secondly, your chosen name should be expressive for your package.

Now this leads to a lot of problems. Consider, for example, that you want to create a package named dom for working with the document object model. Chances are someone has already put a package with that name on npm. On the other hand, let's assume that you need a package for working with DOM. Can you offhandedly run npm install dom and expect to find what you want?

As you can see, a simple name cannot satisfactorily define a package. What we need is some sort of namespace. Scoped packages give you this functionality. Instead of dom, you can name your package @yourname/dom. This prevent name clashes and defines your dom package more thoroughly.

In order to create a scoped package, add --scope yourname to npm init command:

npm init --scope=yourname

This adds a line like the following to your package.json file:

{
"name": "@yourname/dom"
}

When requiring scoped packages, you must use the complete name:

const dom = require("@yourname/dom");

The same applies to including the package as a dependency in package.json:

{
"dependencies": {
"@yourname/dom": "^1.0.0"
}
}

In npm, scoped packages are private by default (and they require paid membership in npmjs.com). If you want to publish your scoped package publicly, you should set the public access option when publishing it (only the first time):

npm publish --access=public

When installing scoped packages, you must use the complete name:

npm install "@yourname/dom"

After installing a scoped package, npm creates a subdirectory @yourname under node_modules and puts your package in that folder:

node_modules
│
└──@yourname
│
└──dom
│
├──package.json
└──index.js

Namespacing is very useful for differentiating packages. Scoped NodeJS packages are already being used in many popular JavaScript projects.

I'm not in a javaScript but have a plan to learn it in the future,
A little c # programmer here :p
the package name is one of the major parts of programming blocks,
It makes us remember what we are doing.
Thanks for sharing this amazing knowledge with us brother.
Yeah, we can say namespace is the backbone of nodejs packages.

Hi @ghasemkiani. I'm currently on a project of creating a local exchange of steem to my local currency(Ghana Cedis) but i have no idea of how to call a user's steemit info when he/she logs in into that site with their steemit account. Thought you could be the best person to help.

Thanks for sharing this! I installed NodeJS on FreeBSD 2 years ago for a developer but i wasn´t fully aware of its structure and capabilities! Am following you, you have my upvote and resteem for this post of yours! Greetings from Mérida, Yucatán, México the Maya Land

Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package.
Each npm user/organization has their own scope, and only you can add packages in your scope. This means you don't have to worry about someone taking your package name ahead of you. Thus it is also a good way to signal official packages for organizations.
Scoped packages can be published and installed as of
npm@2 and are supported by the primary npm registry. Unscoped packages can depend on scoped packages and vice versa. The npm client is backwards-compatible with unscoped registries, so it can be used to work with scoped and unscoped registries at the same time.
Thanks for the post

Your incredible post and the pictures you post are very inspiring to my mind, please support me and give me a lot of upvote and follow me include your comment, hopefully useful, go ahead and hope you succeed in steemit. by @zayanfaruk.