Skip to content

NG SERVE is missing modules when recompiling. #31561

Closed

Description

@juninhocruzg3

🐞 NG SERVE is missing modules when recompiling.

Command (mark with an x)

- [ ] new
- [ ] build
- [X] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

No, It occurs only in ANGULAR CLI 8 generated app

Description

Generating an application with Angular CLI 8 and using ng serve, when editing any code, modules are lost when recompiling.

🔬 Minimal Reproduction

$ ng new portal-sib --enable-ivy --style=scss
$ ng add @angular/material
(import any module - e.g. MatButtonModule - and include html code)
$ ng serve
(Everything works)
(Edit any code and save. After re-compile, mat-button no longer works)

I also tried to import material manually but I get the same error.
I also tried to work without Angular Material but I can't use ngFor in my own module because it works only on first ng serve and miss CommonModule on re-compile.

🔥 Exception or Error

No error is displayed when the problem occurs with the Angular Material. But when I'm using ngFor in my own module, the following error appears:




ERROR Error: Template error: Can't bind to 'ngForOf' since it isn't a known property of 'li'.
    at createUnknownPropertyError (core.js:15130)
    at elementPropertyInternal (core.js:14996)
    at Module.ɵɵproperty (core.js:16581)
    at CarouselBannersComponent_Template (carousel-banners.component.html:6)
    at executeTemplate (core.js:14545)
    at checkView (core.js:15969)
    at componentRefresh (core.js:15727)
    at refreshChildComponents (core.js:14222)
    at refreshDescendantViews (core.js:14128)
    at checkView (core.js:15970)

🌍 Your Environment




Angular CLI: 8.2.0-next.0
Node: 10.14.1
OS: linux x64
Angular: 8.2.0-next.1
... common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.802.0-next.0
@angular-devkit/build-angular     0.802.0-next.0
@angular-devkit/build-optimizer   0.802.0-next.0
@angular-devkit/build-webpack     0.802.0-next.0
@angular-devkit/core              8.2.0-next.0
@angular-devkit/schematics        8.2.0-next.0
@angular/cli                      8.2.0-next.0
@ngtools/webpack                  8.2.0-next.0
@schematics/angular               8.2.0-next.0
@schematics/update                0.802.0-next.0
rxjs                              6.4.0
typescript                        3.4.5
webpack                           4.35.3

Anything else relevant?

This is my first bug report. I hope I have given you enough and clear information. :D

Activity

  1. varadero commented on Jul 15, 2019

    @varadero

    Probably the same problem (most likely related to Ivy) as described in #31560

  2. gkalpak commented on Jul 15, 2019

    @gkalpak
    Member

    Thx for reporting 👍
    I am going to close this, since it does indeed look similar to #31560 (and thus #31512).

    Please, follow #31512 and open a new issue if your problem is not fixed by the fix for #31512.

  3. angular-automatic-lock-bot commented on Sep 15, 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.

  4. locked and limited conversation to collaborators on Sep 15, 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

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions