> We've been working on some updates that will allow Deno to easily import npm packages and make the vast majority of npm packages work in Deno within the next three months. This is really huge and will be a huge boost to the Deno ecosystem. On the other hand, I quite enjoyed that it wasn't jacked into NPM. There were reasonable alternatives like https://jspm.org/. This is a big swing at Node and I'll be watching... - Source: Hacker News / almost 2 years ago

But I really want to make it clear that I'm so incredibly proud of this project and the people who have contributed to it. Snowpack meaningfully pushed the entire web development industry forward, and that's pretty cool. Even if you never use Snowpack directly, the work that we pioneered around npm package handling for ESM is already being built on and improved on across the entire web tooling landscape in... - Source: dev.to / over 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 / 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 / 6 months ago

A local install of Verdaccio running next to our app. - Source: dev.to / 10 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: 12 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: 12 months ago