What is Open-Registry?
To allow people to control the development, funding and support of the registry itself, by making it fully open-source and transparent for its user and the public
Open-Registry is a tool in the Front End Package Manager category of a tech stack.
Open-Registry is an open source tool with 253 GitHub stars and 6 GitHub forks. Here’s a link to Open-Registry's open source repository on GitHub
Who uses Open-Registry?
Why developers like Open-Registry?
Here’s a list of reasons why companies and developers use Open-Registry
Be the first to leave a pro
- Serves a full mirror of the npm registry
- Take a look at our roadmap
- Funded by the community
- Governed by the community
Open-Registry Alternatives & Comparisons
What are some alternatives to Open-Registry?
See all alternatives
Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.
Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
Browserify lets you require('modules') in the browser by bundling up all of your dependencies.