Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bug([@angular/material*]): Packages won't be catched by ngcc anymore | v9.1.1

See original GitHub issue

Reproduction

Steps to reproduce:

npm i @angular/compiler @angular/compiler-cli @angular/core @angular/material @angular/cdk tslib typescript@3.7.5
run ngcc --properties es2015 --first-only --create-ivy-entry-points

Expected Behavior

What behavior were you expecting to see?

@angular/material packages to be compiled by ngcc like before.

Actual Behavior

What behavior did you actually see?

@angular/* packages and @angular/cdk will be compiled by ngcc but @angular/material not

Environment

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 9.0.5
Node: 12.16.0
OS: win32 x64

Angular: 9.0.5
... cli, common, compiler, compiler-cli, core, elements, forms
... platform-browser
Ivy Workspace: Yes

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.900.5
@angular-devkit/build-ng-packagr   0.900.5
@angular-devkit/core               9.0.5
@angular-devkit/schematics         9.0.5
@angular/cdk                       9.1.1
@angular/material                  9.1.1
@schematics/angular                9.0.5
@schematics/update                 0.900.5
ng-packagr                         9.0.2
rxjs                               6.5.4
typescript                         3.7.5

cheers flash ⚡

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

flash-mecommented, Mar 5, 2020

This indeed solves the issue. Thanks for the hint! From my side this issue can be closed.

Cheers flash ⚡

1reaction

devversioncommented, Mar 5, 2020

Thanks for the issue. I just tried your command, and I was able to reproduce the described issue.

The problem here is that ngcc is unable to process all entry-points if they have missing dependencies. e.g. Angular Material depends on @angular/common.

When I added the required dependencies, ngcc was able to process all entry-points as expected.