Repository navigation
Components not rendered when added to other components when Ivy is enabled #31570
Description
🐞 bug report
Description
I created a new project with —enableIvy flag. Worked fine until I created a new component using the cli, and added the component to the app component, while the app was being served. On live reload the new component was not rendered, although the dev tools showed that it was there. So I had to “re-serve” the app for the new component to appear in the app.
Moreover, when I created another new component and also added it to the app component, all the components added to the app component disappeared. Again I had to restart the app for all the components to be displayed.
🔬 Minimal Reproduction
ng new test-app —enable-ivyng g c testng s- paste test component element into the app component template, like so
<app-test><app-test>, and save. - check out the tab with your app in your favorite browser
🔥 Exception or Error
Dev tools as well as the cli don’t show any errors.
🌍 Your Environment
Angular Version:
Angular CLI: 8.1.1
Node: 10.15.2
OS: darwin x64
Angular: 8.1.1
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.801.1
@angular-devkit/build-angular 0.801.1
@angular-devkit/build-optimizer 0.801.1
@angular-devkit/build-webpack 0.801.1
@angular-devkit/core 8.1.1
@angular-devkit/schematics 8.1.1
@ngtools/webpack 8.1.1
@schematics/angular 8.1.1
@schematics/update 0.801.1
rxjs 6.4.0
typescript 3.4.5
webpack 4.35.2
Anything else relevant?
Using MacBook Pro Early 2011, OS: HighSierra 10.13.6, IDE: VSCode, terminal: bash
Activity
alexzuza commentedon Jul 15, 2019
Appears related to #31512
rip222 commentedon Jul 15, 2019
are you sure? My app produces no errors
alxhub commentedon Jul 16, 2019
@rip222 can you please add detailed, step by step directions for reproducing this problem?
rip222 commentedon Jul 19, 2019
done
simply-alliv commentedon Oct 28, 2019
I am having the exact same issue. Has there been any developments since this issue was opened?
JoostK commentedon Nov 1, 2019
I'm hopeful that #33522 will resolve this issue.
JoostK commentedon Dec 16, 2019
This issue should have been resolved with recent fixes to incremental rebuilds. As there's no reproduction available I'm going to assume this issue has indeed been resolved. If someone is still seeing issues with incomplete incremental rebuilds, please open a new issue.
angular-automatic-lock-bot commentedon Jan 16, 2020
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.