Priority in secondary packages

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

I have multiple secondary packages for my library my-lib as follows:

• my-lib/defaults
• my-lib/testing

However, my-lib/testing depends on my-lib/defaults and therefore my-lib/defaults needs to make sure it is built before my-lib/testing. Is there a way to ensure that the defaults package is built before the testing package?

Version Information

ng-packagr: 3.0.2
@angular/*: 6.0.4
@angular-devkit/build-ng-packagr: 0.6.8
@angular-devkit/build-angular: 0.6.8
typescript: 2.7.2
rxjs: 6.0.0
node: 8.11.2
yarn: 1.7.0

[alan-agius4]

This is done automatically. As ng-packagr analysis the dependencies and builds a dependency graph used to build the entry points in order

[Hobart2967]

This is anyhow not working.

using a class exported from

module/entryPointA/src/class1.ts => import {class2} from ‘module/entryPointB’;

while entryPointB exports class2 it shows:

Cannot find module ‘module/entryPointB’.

As it’s not built yet…