So we can change the package to be published publicly when we initially publish with the access argument: npm publish -access public The thing is we cannot publish privately into the primary registry, unless we have a paid account. Having said that, we should be aware that the package is published privately by default, meaning with restricted access. In order to do that, we should merely run the npm publish command: npm publish Great, let’s communicate with the registry and publish our package. In case we do want to assign the scope with a private registry, we can use npm config command and set it in advance: npm config set Basically there are two options for choosing a registry to publish into - it could be the primary of npm or a private registry which we maintain ourselves. Now that we have an initialized local scoped package, we’d like to communicate with an npm registry to publish this package (and install as well later).

In case the package has already been initialized, we will just need to rename it to contain the scope according to the convention, nothing more. In order to create a new local scoped package, we can use npm init -scope=sample-scope, which creates a package.json file and names the package considering the provided scope: 'name': that there is a convention so that the scope name itself begins with and followed by a slash. So, let’s demonstrate how to work with scoped packages practically. That being said, there’s no free lunch, and we need to know how to use them correctly - but that’s the purpose of this guide.

In case we work with a private npm registry - we don’t have to switch to it before installing or publishing a package, but rather simply set the private registry for the scope in advance and once.

We don’t have to worry that someone else will publish into our scope - only scope members have the permission.

We don’t have to worry if the package name exists - just name it, as long as we haven’t already published such a scoped package before.

This kind of packages provides a few benefits:

Scoped Packages is a way to group related npm packages together, and connect them to each other by a specified “scope”, that acts pretty much like a namespace.

If you like this kind of work, you can save the full playlist and subscribe to my YouTube channel today to not miss new content.

Npm config set private registry