title: How to build a dependency when running an Angular project
body: <p>In the company where I work we have several Angular projects, each one having a common project as a dependency in the <code>package.json</code>. This common project contains common components or pipes.</p>
  <p>Whenever we need to modify a component of the common project we have to run <code>npm run packagr</code> and then <code>npm publish</code> from the <code>dist</code> folder. The common project is then deployed in a nexus repository from which each projects that requires it download the dependency with a <code>npm install</code>.</p>
  <p>I joined the company when this structure was already running. This process bothers me and pushes me to look for a different solution to run (or compile) the common project together with the primary project at the <code>npm start</code> action.</p>
  <p>I found possible way by reading the Angular documentation on <a href="https://angular.io/guide/creating-libraries" rel="nofollow noreferrer">libraries</a>, but I'm not that experienced in Angular and as far as i understand project and library should be in the same folder.</p>
  <p>In our structure, both the projects and the common project are located in different folders each linked to its own git repository.</p>
  <p>When a I work on a Java project, Eclipse takes care of compiling the dependencies (previously imported in the workspace) for me by reading the pom.xml.
  Is there any way to get the same result when I run <code>npm install</code> of a project, my dependencies are also built?</p>