Angular library ng-packagr doesn’t replace tsconfig paths with relative paths

The only solution I found is to choose a prefix so that your paths will be exactly the same when the package is installed in node_modules

For example, if your package name is xyz, you tsconfig will be:

"paths": {
  "xyz/*": ["lib/*"]
}

I highly recommend using sub-entries as it not only solved this issue, but also it’ll support tree shaking. This article will help

CLICK HERE to find out more related problems solutions.

Leave a Comment

Your email address will not be published.

Scroll to Top