Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
e7c2e65c fix(angular): import optional `ng-packagr` lazily (#36632) `@nx/angular/executors` eagerly loads the package executor path, which loads `ng-packagr` at module evaluation time via `packages/angular/src/executors/package/ng-packagr-adjustments/ng-packagr.ts`. ## Current Behavior Today this can break Angular application builds in downstream wrappers that import `@nx/angular/executors` only to call the webpack browser builder, because the barrel import evaluates the package executor path and throws `Cannot find module 'ng-packagr'` before any library-packaging code is selected. ## Expected Behavior - app-build imports from `@nx/angular/executors` should work without `ng-packagr` - `ng-packagr` should only be required when `@nx/angular:package` or related library packaging executors actually run ## Related Issue(s) none --------- Co-authored-by: Benjamin Brienen <Benjamin.Brienen@cpp.canon>
by BenjaminBr...
Succeeded
master
e7c2e65c fix(angular): import optional `ng-packagr` lazily (#36632) `@nx/angular/executors` eagerly loads the package executor path, which loads `ng-packagr` at module evaluation time via `packages/angular/src/executors/package/ng-packagr-adjustments/ng-packagr.ts`. ## Current Behavior Today this can break Angular application builds in downstream wrappers that import `@nx/angular/executors` only to call the webpack browser builder, because the barrel import evaluates the package executor path and throws `Cannot find module 'ng-packagr'` before any library-packaging code is selected. ## Expected Behavior - app-build imports from `@nx/angular/executors` should work without `ng-packagr` - `ng-packagr` should only be required when `@nx/angular:package` or related library packaging executors actually run ## Related Issue(s) none --------- Co-authored-by: Benjamin Brienen <Benjamin.Brienen@cpp.canon>
by BenjaminBr...
Succeeded
23.2.0-beta.12
e7c2e65c fix(angular): import optional `ng-packagr` lazily (#36632) `@nx/angular/executors` eagerly loads the package executor path, which loads `ng-packagr` at module evaluation time via `packages/angular/src/executors/package/ng-packagr-adjustments/ng-packagr.ts`. ## Current Behavior Today this can break Angular application builds in downstream wrappers that import `@nx/angular/executors` only to call the webpack browser builder, because the barrel import evaluates the package executor path and throws `Cannot find module 'ng-packagr'` before any library-packaging code is selected. ## Expected Behavior - app-build imports from `@nx/angular/executors` should work without `ng-packagr` - `ng-packagr` should only be required when `@nx/angular:package` or related library packaging executors actually run ## Related Issue(s) none --------- Co-authored-by: Benjamin Brienen <Benjamin.Brienen@cpp.canon>
by BenjaminBr...
Failed
master
e7c2e65c fix(angular): import optional `ng-packagr` lazily (#36632) `@nx/angular/executors` eagerly loads the package executor path, which loads `ng-packagr` at module evaluation time via `packages/angular/src/executors/package/ng-packagr-adjustments/ng-packagr.ts`. ## Current Behavior Today this can break Angular application builds in downstream wrappers that import `@nx/angular/executors` only to call the webpack browser builder, because the barrel import evaluates the package executor path and throws `Cannot find module 'ng-packagr'` before any library-packaging code is selected. ## Expected Behavior - app-build imports from `@nx/angular/executors` should work without `ng-packagr` - `ng-packagr` should only be required when `@nx/angular:package` or related library packaging executors actually run ## Related Issue(s) none --------- Co-authored-by: Benjamin Brienen <Benjamin.Brienen@cpp.canon>
by BenjaminBr...