Other popular posts
Hey all, wanted to give a simple update here about changes that we made to our hosted Private npm product. This change makes it easier for you to use the
npm client you know and love to access information about your private modules.
We now return only private package metadata for "list" routes. These routes (e.g. http://registry.npmjs.org/-/all) interact with the
npm search command. This works by using your Nodejitsu Private NPM URL to ensure it is routed to your registry just like packages. This means that you can now easily search across just your private packages:
npm i -g npm npm c set registry https://your-private.registry.nodejitsu.com npm search private-something
For those of you who don't know, our Private NPM product is based on a
smart-private-npm proxy that knows how to talk to the CouchDB routes the registry is based around.
We had previously had a notion that we wanted to merge both public and private registry package streams into a single data stream in the proxy layer. As the public npm registry grows in size, streaming all the public JSON back proved to be a massively iefficient solution. So, when one of our customers recently needed a dynamic way to get all of their private packages, we decided to make the change to private by default.
First off, the public search you know and love is still available if you pass in the
npm --reg=http://registry.nodejitsu.com search public-something
You might even want to setup an alias for that:
alias pubnpm="npm --reg=http://registry.nodejitsu.com"
Lastly, if you are looking for private package needs in your development workflow NOW, check out our product and let us know what you think!