Skip to content

[ivy] app doesn't work when ng-packagr library is used #32080

Closed

Description

@fr0

🐞 bug report

Affected Package

Ivy

Is this a regression?

Yes, works in non-ivy

Description

See repo below.

  1. Run with --prod and --aot (otherwise you will run into [ivy] ERROR Error: Template error: Can't bind to 'ngForOf' since it isn't a known property of 'div'. #32078)
  2. Open http://localhost:4200/route1
  3. Notice that the items from the ngFor do not appear.
  4. Change enableIvy to false in src/tsconfig.app.json and run again
  5. Notice that the items appear.

🔬 Minimal Reproduction

https://github.com/fr0/angular-test/tree/ivy

🔥 Exception or Error

There is no error. The app just doesn't work like it does in non-Ivy.

🌍 Your Environment

Angular Version:




Angular CLI: 8.3.0-next.1
Node: 12.6.0
OS: darwin x64
Angular: 9.0.0-next.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.0-next.1
@angular-devkit/build-angular     0.803.0-next.1
@angular-devkit/build-optimizer   0.803.0-next.1
@angular-devkit/build-webpack     0.803.0-next.1
@angular-devkit/core              8.3.0-next.1
@angular-devkit/schematics        8.3.0-next.1
@angular/cli                      8.3.0-next.1
@ngtools/webpack                  8.3.0-next.1
@schematics/angular               8.3.0-next.1
@schematics/update                0.803.0-next.1
ng-packagr                        5.4.3
rxjs                              6.5.2
typescript                        3.5.3
webpack                           4.38.0

Activity

  1. added this to the needsTriage milestone on Aug 9, 2019
  2. angular-automatic-lock-bot commented on Oct 20, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  3. locked and limited conversation to collaborators on Oct 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions