I was told in another forum to look at Private Packagist... But how is that different? Instead of installing packages from packagist.org.. You pay to Packagist.com to do the same thing? You just download from packagist.com cloud instead of packagist.org? Source: almost 2 years ago

We have a private Satis instance. Our ITSec team reviews all packages before we add them to Satis. Packagist.com is available for us but the CI-CD servers can reach only the private Satis. Source: almost 2 years ago

Https://packagist.com maybe tell them about a local packagist install. Source: almost 2 years ago

"[MANAGER] requested this to be done in PHP. You as IT will know that most modern programming and scripting languages work only with packaging software properly. Composer sends requests (majority of cases) to packagist.com and to github.com. It will add thousands of hours to do everything that composer does manually. Please sign here to authorize the usage of 4000 hours and the possible delay of 4000 hours.... Source: almost 2 years ago

Another downside that only really exists with non-PHP boilerplates is getting updates isn'T as easy. With PHP we're able to use packagist.com and make our code available via composer. Other languages don't have this so SaaS Pegasus provides zip downloads and Gravity provides access to a GitHub repo. This means you have to apply bug fixes yourself. With Parthenon, you do composer update and you'll get the latest... Source: almost 2 years ago

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