Distributing angular libraries inside enterprise?
Am new to angular, 3 days into my crash course at a new enterprise. I'm trying to understand how angular libraries should be distributed within an enterprise.
However what I am seeing is a dependency on use non or bit to upload our library to there system and manage it from there. Is there no way to package a library and distribute to projects within our org that does not rely on third parties?
Posted Jan 23, 2020, 2:58 PM UTC
38
You can create you own private packages with NPM. That's how my organization does it. https://docs.npmjs.com/creating-and-publishing-private-packages
Your link clearly says its publishing the package to npm registry, albeit with user or private scope.
What I want is a local npm package server that I controll and when I submit and npm install command, it goes to my personal server.
You can use git.
https://mskutta.github.io/2018/05/25/private-npm-packages-in-bitbucket/
You can also use a Azure DevOps Artifact feed as a private NPM repo.
This, this is best solution for me.
You can use https://github.com/verdaccio/verdaccio for that purpose.
All ubiquitous package hosts are going to be a private repository on a 3rd party's cloud. You will be stepping into the fringe if you want to host the repo on-prem.
I use a private npm repo hosted in my org's azure devops instance.