Verdaccio might be a bit more popular than Artifactory. We know about 27 links to it since March 2021 and only 20 links to Artifactory. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Another option is to publish our package is with azure artifacts, npm with free version public. But if we want to make it private, we need to pay or set up our own private npm repository. In this moment is where Verdaccio comes in to help us. - Source: dev.to / about 2 months ago
And finally, we extracted our own Verdaccio setup that we've been using to run our e2e tests in the Nx repo s.t. You can use it for your own plugin development as well. Check out this video for a walkthrough on how this works. - Source: dev.to / 5 months ago
A local install of Verdaccio running next to our app. - Source: dev.to / 9 months ago
You may want to look into setting up a “Private NPM Registry”. My company maintains 5-6 apps and have many shared libraries just like you describe. We use Verdaccio. I don’t know our costs. Source: 11 months ago
All my source code is in GitHub, I run my own private NPM Registry (Verdaccio) for my private packages and it also acts as a cache, and I use pnpm instead of npm. Source: 11 months ago
I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 11 months ago
When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago
Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago
Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: over 1 year ago
If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago
Sonatype Nexus Repository - The world's only repository manager with FREE support for popular formats.
npm - npm is a package manager for Node.
Cloudsmith - Cloudsmith is the preferred software platform for securely storing and sharing packages and containers. We have distributed millions of packages for innovative companies around the world.
Bytesafe - A better way to control your software supply chain
Atlassian Bitbucket Server - Atlassian Bitbucket Server is a scalable collaborative Git solution.
jFrog - Host, manage and proxy artifacts using the best Docker Registry, Maven Repository, Gradle repository, NuGet repository, Ruby repository, Debian repository npm repository, Yum repository.