A private npm registry and backup server that caches packages locally or in S3, providing fast, reliable access even when npmjs.org is down.
npm-register is a self-hosted npm registry and backup server that caches packages from npmjs.org locally or in cloud storage. It provides a private registry for hosting internal packages and ensures continuous access to dependencies even when the public npm registry is offline. The project acts as a caching proxy, storing metadata and tarballs for previously accessed packages to maintain availability during outages.
Development teams and organizations needing a private npm registry for internal packages or a reliable backup solution to mitigate npmjs.org downtime. It's also suitable for DevOps engineers managing self-hosted infrastructure.
npm-register offers a lightweight, easy-to-setup alternative to full registry mirrors, focusing on caching for performance and reliability. Its support for multiple storage backends, 12 Factor app design, and compatibility with standard npm commands make it a flexible and maintainable choice for private package management.
Your own private npm registry and backup server
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports one-click deployment on Heroku and global npm installation, simplifying setup for various platforms as shown in the README.
Allows storage on local filesystem, Amazon S3, or Google Cloud Storage, enabling scalability and durability based on needs, detailed in the storage sections.
Caches package metadata and tarballs, providing faster access than npmjs.org and ensuring availability during outages, as emphasized in the overview.
Includes a --always-https flag to ensure seamless compatibility with Yarn, addressing its HTTPS expectations as noted in the compatibility section.
Adheres to the 12 Factor methodology, making it easy to deploy on PaaS like Heroku and maintain in cloud environments, highlighted in the philosophy.
Missing support for npm commands like star and search, and potentially other functionalities, as explicitly noted in the README's supported commands section.
Requires manual creation and management of htpasswd files with commands like aws s3 cp, which can be cumbersome and lacks a graphical interface.
For full features like authentication, it relies on external services like S3, adding setup complexity and ongoing costs, as seen in the S3 storage requirements.
Only caches accessed packages, so it cannot serve as a complete backup for all npm packages, limiting offline usability, as stated in the overview.