The Next Level of npm Support with Nexus [VIDEOS]

Publishing npm Packages

Author, Manfred Moser

I has been quite a while since I last wrote about support for npm in the Nexus Repository Manager. Back then I was very excited to announce that with version 2.9 we are offering npm support to everyone for free with the OSS edition. Since then it has been used by a lot of you and we have been working hard on version 3 of the Nexus Repository Manager.

npm Registries

With the recent release of milestone 6 of Nexus Repository Manager OSS 3, support for npm registries has gotten a whole lot better again. And to celebrate and show you how easy it is to get started I made some video demos.

Using the Nexus Repository Manager as a Javascript developer using Node.js, grunt and many other tools, npm is a familiar package manager to you. And the npmjs registry is your source of convenient access to a myriad of packages. Adopting the Nexus Repository Manager allows you to cache any downloads from this registry and any other available package registries. This will improve the stability and performance of your builds and usage of npm.

More importantly however, you get to have your own private registry in the repository manager. You can host your own, internal packages and share them with others in your organization. This can include other developers and development teams, but also continuous integration servers, test setups or even production deployments.

And getting this all setup can be done in a couple of minutes. Check out the videos showing it all in action and use the documentation as a guide to get it all done in your own deployment.

The Videos

Here are two videos on getting started with npm, and publishing npm pages to the Nexus repository. There are 30 videos in the complete “Tips from the Trenches” Series, available for free to TheNEXUS Community members.

 

How it works

It all boils down to a few simple steps to get the caching of packages working

  • Download and install the Nexus Repository Manager
  • Configure npm repositories
  • Change the default registry for npm in .npmrc

And if you want to publish your own packages to the Nexus Repository Manager you just have to

  • Activate the npm security realm
  • Authenticate with npm login
  • Update your package.json with a publishConfig
  • Run npm publish

It’s is really that simple.

Compared to version 2, the version supports browsing in your npm repositories. You can search for specific packages and inspect their assets. npm login support makes authentication easier too.

So what are you waiting for? Get Nexus Repository Manager OSS 3 to access all these benefits. And once you have installed it for your npm usage, tell the rest of your team. You  could use the same server for usage with

  • Maven-format repositories for JVM based development, or
  • NuGet-format repositories for .Net development or
  • Docker-format registries

Get a boost in your DevOps efforts with the free Nexus Repository Manager OSS 3. You gonna love it.

The following two tabs change content below.

Manfred Moser

Manfred Moser is trainer, author and community advocate at Sonatype working on efforts around the Nexus Repository Manager, the Nexus IQ Server and the Central Repository. He is a regular speaker at conference such as JavaOne, AnDevCon, OSCON and others.. Fluent in both German and English, he also speaks and writes Java and a bunch of other programming languages and uses these skills as committer and project lead on a number of open source projects such as the Android Maven Plugin. The open source community and open source software has been a passion of his for well over a decade and he is sure it will be for a few more decades. Manfred can be found on most social channels, including Twitter, LinkedIn and Google+.
Authors

Related posts

2 Comments

  1. mike said:

    I am using Nexus OSS 3.0.0-b2015091801. When I try to follow your directions I notice that NPM is not an option. It is not an option when I try to create a repository, it is not in the list of available realms, etc. Is there anything I need to do to enable NPM?

    Thanks for any help you can provide.

    • mike said:

      Looks like all I had to do is install 3.0.0-b2015110601 instead and I now have NPM support.

*

Top