It's very popular (8.5k GitHub stars), actively maintained as of (), has many questions asked/answered about it on Stack Overflow in addition to excellent documentation on it's website. However, if we didn't have ProGet already setup, I would have chosen Verdaccio. It made sense to just use this and add an NPM registry alongside the NuGet registry. ![]() The main reason behind this decision was that we were currently self-hosting ProGet which was being used for our NuGet packages. We chose ProGet to host our private NPM registry that would initially host the component library, and later, all other future RateSetter NPM packages. The downside is that there is usually overhead with setting up these services as they are required to be self-hosted. free and all the packages are hosted on your servers. Freeīenefits of free services are that they are. It's important to note that while some services are more expensive that others, they offer additional features like hosting other package libraries like NuGet (.Net), Maven (Java) and Gems (Ruby). The downside is that you have to pay for the service and risk having your packages removed if they violate the services T&Cs or compromised in the unlikely event of a breach. You also receive great documentation and support that help you use the service. There is little to no configuration required. The benefits of paid service is that you receive a working solution out of the box. There are two options for hosting a private NPM registry for your organisation: Paid ![]() Choosing an NPM Registryįirst up, we have to choose how we want to host our registry. Note: For this article I'll be creating a scoped NPM package: Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package. The component library being an NPM package met all these requirements. Versioning was essential as we needed to be able to manage this evolving library being used in a number of projects throughout the company. Private hosting was required as we only wanted engineers at RateSetter to see and use the package. ![]() With the RateSetter component library all set up, we now needed a way to privately host, distribute and manage versioning it. This article follows on from how I setup a React component library at work.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |