Is node.js your thing? Maybe npmjs.org is the home page on your browser. Need your very own Npm registry?
Well, you’re not alone. The vast majority of enterprise level companies make extensive usage of binary components such as free open-source libraries and commercial libraries as well as proprietary libraries built in-house. Over 300 Million packages were downloaded from npmjs.org during May 2014. While it’s great to save time and resources by using 3rd party components, it also presents several challenges:
Npmjs.org may not always be accessible – it may go down or there may be networking problems. This hampers development and delays builds. Then there’s the question of security. You may want to restrict what developers can download from external sources, and then control who can access downloaded components. You also need to organize your own proprietary packages, and share and distribute them with other development teams, some of which may be at remote geographical sites of your enterprise. And with the multitude of components you are using, finding that particular version of a specific component can sometimes be tricky.
Your Very Own Local Npm Registry
Local Repositories give you a place to manage your proprietary packages and an easy way to share them with your team members and other teams
Proxy and Cache Any Remote Npm Registry
Remote Repositories ensure reliable access to external resources by proxying them and caching downloaded packages locally
Comprehensive security measures give you fine-grained control over which packages can be downloaded, where they can be put, and who can access them.
Smart search capabilities make it easy to find a package based on both inherent and custom properties.
These features and many more can reduce your development and build time by addressing the many challenges you face when developing with components from any packaging system.