4 ms·
I was doing some research recently on various private NPM registry implementations. My company wanted a way to share internal libraries and frontend apps in the
by eberkund 7y ago
I was doing some research recently on various private NPM registry implementations. My company wanted a way to share internal libraries and frontend apps in their local network. I was surprised to find out how poor most of the options were. I ended up settling on Azure DevOps (self-hosted) but an open-source fork of NPM wouldn't be the worst thing in the world. If the infrastructure went down tomorrow I'm sure most people could switch to Yarn without too much trouble.
- ssalka 7y ago>If the infrastructure went down tomorrow I'm sure most people could switch to Yarn without too much trouble. Generally true, except in the case of private scoped NPM packages. AFAIK if you want to switch to the yarn registry then you need to add exceptions that map your scoped package names to repositories that you host elsewhere.
- krainboltgreene 7y agoThere's no such thing as a yarn registry. The uri is just a CNAME to npm Inc.
- doublerebel 7y agosmart-private-npm is nearly API-compatible, I've been using it for years.
- krainboltgreene 7y agoIf npm is down, so is yarn. Yarn's registry url is just a CNAME to npm Inc's registry.