angular-cli: ng build v6 does not use paths section of root tsconfig.json

Solved the problem in Angular 7 adding the paths to both tsconfig files

• paths in tsconfig.json helps vscode to works and with intellisense
• paths in tsconfig.app.json is also needed for angular

tsconfig.json

tsconfig.app.json

and the intellisense works great

I was trying to create a mono repo project and I stumble upon the same issue. After hours of diagnosing the issue, I reached out the same conclusion @krotscheck mentioned. NgPackagr will overwrite baseUrl to the entry point, which is src/public_api (see line 44).

The workaround is manually adding the path to either tsconfig.json in root, or tsconfig.lib.json in lib. I still find this solution weird since the path ../../../dist/my-library is very very relative.

one more thing

The same thing well happen if you want to reference your lib in another app, you have to add another path relative to the app directory this time not relative to src. Of course this is not related to ng-packagr. Your tsconfig.json will end up something like this:

{
  "compilerOptions": {
    ...,
    "paths": {
      "my-library": [
        "dist/my-library", // mostly for the IDE
        "../../dist/my-library", // for the app
        "../../../dist/my-library" // for another lib
      ]
    }
  }
}

Solved the problem in Angular 7 adding the paths to both tsconfig files

• paths in tsconfig.json helps vscode to works and with intellisense
• paths in tsconfig.app.json is also needed for angular

tsconfig.json

tsconfig.app.json

and the intellisense works great

IDE Restart required (VSCODE)

I have the same issue but when I look back the whole structure of angular 5 app and I found that there is one more tsc file with name is tsconfig.app.json at src folder. it extends from tsconfig.json. We need to declare alias paths with the relative path of tsconfig.app.json instead of tsconfig.json location. It works properly now. tsconfig.app.json: { "extends": "../tsconfig.json", "compilerOptions": { "outDir": "../out-tsc/app", "baseUrl": "./", "paths": { "@shared/components/*": [ "app/shared/*" ], "@shared/services/*": [ "app/services/*" ] }, "module": "es2015", "types": [] }, "exclude": [ "test.ts", "**/*.spec.ts" ] }

if tsconfig.app.json extend tsconfig.json then you only need to add it to tsconfig.json and then restart VSCode. Example with angular8

    "paths": {
      "@core/*": [
        "src/app/core/*"
      ],
      "@store/*": [
        "src/app/app-store/*"
      ]
    },```

Confirmed, I’ve got it working, though it required more than just an ‘out-of-the-box’ experience. The changes I needed were:

1. add a custom tsconfig.lib.json link inside angular.json

        "build": {
          "builder": "@angular-devkit/build-ng-packagr:build",
          "options": {
            "project": "projects/my-library/ng-package.json",
            "tsConfig": "projects/my-library/tsconfig.lib.json"
          },
          "configurations": {
            "production": {
              "project": "projects/my-library/ng-package.prod.json"
            }
          }

1. Create the tsconfig.lib.json file.

{
  "extends": "../../tsconfig.json",
  "compilerOptions": {
    "target": "es6",
    "inlineSources": true
  }
}

1. Most importantly, add another path to the root tsconfig, OR an appropriate block to the library’s own tsconfig. Here’s the root version, for the lib version, remember that baseUrl is overridden to src, so you have to add another ../

{
  "compilerOptions": {
    ...,
    "paths": {
      "my-library": [
        "dist/my-library",
        "../../../dist/my-library"
      ]
    }
  }
}

@hansl - I’d be happy to add this to the library schematic, however I’m not quite certain how to manage paths generation of the tsconfig.json file, nor whether it should be done at the root or at the library level. Do you have any guidance?