title: Using Typescript paths mapping in Angular library
body: <p>I'm currently developing a small Angular library. To shorten some imports I've used <code>paths</code> mapping in <code>tsconfig.json</code>. However, after building the library, imports in emitted <code>.js</code> files (in ES2015 version) are not changed, because the path mapping is for Typescript transpiler only. </p>
  
  <p>My question is, how can I assure the imports have the right paths without having to sacrifice the <code>paths</code> mapping functionality. I've read an <a href="https://github.com/microsoft/TypeScript/issues/10866" rel="nofollow noreferrer">issue on GitHub about the module paths in emitted files</a> but haven't found any suitable solution.</p>