How to update examples/angular_bazel_architect to use @angular-devkit/build-angular:ng-packagr

[bbergquist0930]

I am trying to update the example to use @angular-devkit/build-angular:ng-packagr. The bazel build completes with no errors

Building Angular Package
******************************************************************************
It is not recommended to publish Ivy libraries to NPM repositories.
Read more here: https://v9.angular.io/guide/ivy#maintaining-library-compatibility
******************************************************************************

------------------------------------------------------------------------------
Building entry point 'frontend-lib'
------------------------------------------------------------------------------
Compiling TypeScript sources through ngc
Bundling to FESM2015
Bundling to UMD
Minifying UMD bundle
Writing package metadata
Built frontend-lib

------------------------------------------------------------------------------
Built Angular Package
 - from: /home/brett/.cache/bazel/_bazel_brett/334579670018687448fe7d37f10fc324/sandbox/linux-sandbox/2/execroot/angular_bazel_architect/projects/frontend-lib
 - to:   /home/brett/.cache/bazel/_bazel_brett/334579670018687448fe7d37f10fc324/sandbox/linux-sandbox/2/execroot/angular_bazel_architect/dist
------------------------------------------------------------------------------
SUCCESS
Result: {
    "success": true,
    "target": {
        "project": "frontend-lib",
        "target": "build"
    }
}

Logs:
Target //projects/frontend-lib:build up-to-date:
  dist/bin/projects/frontend-lib/build
INFO: Elapsed time: 3.873s, Critical Path: 0.47s
INFO: 9 processes: 1 remote cache hit, 8 internal.
INFO: Build completed successfully, 9 total actions
INFO: Build completed successfully, 9 total actions

however nothing is produced

brett@brett-Precision-7740:~/git/rules_nodejs/examples/angular_bazel_architect$ ls dist/bin/projects/frontend-lib/build/
brett@brett-Precision-7740:~/git/rules_nodejs/examples/angular_bazel_architect$ 

Any ideas of what I am missing?

Here is a patch of what I changed

patch.txt

[bbergquist0930]

Actually I believe I figured out the issue. I tried changing the sample to use a standard ng-packagr configuration file ng-package.json and did not realize that what was actually being done was that builder was interpreting the javascript file ng-package.js and that is determining the build directory and then creating the configuration on the fly with that destination and returning that.