title: Angular libraries : How to switch from npm package to npm sym link?
body: <p>Within my Angular workspace, I have one Application and one Library.</p>
  <p>The library is referenced in the application using a sym link (<code>npm link my-lib</code>) and I updated my <code>tsconfig.json</code> to know about the path of my library:</p>
  <pre><code>&quot;paths&quot;: {
    &quot;my-lib&quot;: [
      &quot;dist/my-lib/my-lib&quot;,
      &quot;dist/my-lib&quot;
    ]
  }
  </code></pre>
  <p>When I build my library like this :</p>
  <p><code>ng build my-lib --watch</code></p>
  <p>I get live updates, I can instantly see the changes in my Application which is recompiled automatically when using <code>ng serve</code></p>
  <p>Up to this point it's all good. However when I build on my build server, I want to publish my library to npm and use the npm package instead of a sym link.</p>
  <p>After publishing my package to npm, I ran <code>npm i my-lib</code> in my Application. The package is installed.</p>
  <p>However I no longer get live updates when making changes to my libraries in development. I think this is because the sym link is no longer used and my Application is using the npm package instead.</p>
  <p>How do I work around this problem ?  I need the package for production, but in development I want to use the sym link. How can I do that ?</p>