bennadel / Component-Queries-Ivy-Bug-Angular9

Isolation case for possible Ivy ??bug?? in Angular 9.0.0-rc.2

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

README.md

Possible Component Queries Bug When Running Ivy In Non-Production Mode In Angular 9.0.0-rc.2

UPDATE: 2019-11-19 - Jeffrey Bosch was able to figure out what was going on. He moved my "aot":true configuration up from the production options and into the core build options. Apparently this was part of a CLI migration a while back. But, I don't use the CLI on an ongoing basis; really, I just copy-paste one configuration from one demo to another.

Huge thanks to Jeffrey!


This is an isolated repository for a potential bug in Ivy - or something that interacts with Ivy - in the development server provided by the Angular CLI. This project has only two run-scripts:

"scripts": {
	"start-dev": "ng serve --open",
	"start-prod": "ng serve --open --prod"
},

If you run this using npm run start-dev, you get the following output:

And, if you run this using npm run start-prod, you get the following output:

As you can see, in the dev mode, only the @ViewChild() property annotation works. However, in the prod mode, both approaches work.

About

Isolation case for possible Ivy ??bug?? in Angular 9.0.0-rc.2


Languages

Language:TypeScript 92.6%Language:HTML 6.7%Language:CSS 0.7%