ng build --prod --watch compiles app state before the save

[bklik]

Description:

While running a build watch with the '--prod' or '--aot' options, the results to dist seem to be one save behind. Meaning, if I make a change and save, the change is detected and the project builds, however the results are the state of the app before the change. If I make another change, like adding a new line to a file, the change is detected and the project built, with the results of the previous save but not capturing the new lines added.

Note: This issue goes away if the '--prod' or '--aot' options are not used.

OS?

Windows 10

Versions.

@angular/cli: 1.0.0-beta.30
node: 6.9.5
os: win32 x64
@angular/common: 2.4.8
@angular/compiler: 2.4.8
@angular/core: 2.4.8
@angular/forms: 2.4.8
@angular/http: 2.4.8
@angular/platform-browser: 2.4.8
@angular/platform-browser-dynamic: 2.4.8
@angular/router: 3.4.8
@angular/cli: 1.0.0-beta.30
@angular/compiler-cli: 2.4.8

Repro steps.

ng new test-app
ng build --prod --watch
or
ng build --aot --watch
or
ng build --prod --aot --watch

The log given by the failure.

None

[bklik]

After solving issue #5138 this problem went away. My guess is I somehow had multiple versions of angular-cli installed that were conflicting with each other.

[bklik]

Correction, I'm still experiencing this issue on another computer after following the same steps I used to solve #5138 . I found that if I make a change to the index file, I can see the change take immediate effect in the dist folder. However, a change to a component does not show up, and is always one save behind.

[lbialy]

Same here, build -w --aot outputs first compilation result correctly, but then every next rebuild is one save behind (I have to make 2 changes & saves to see result of first change). Doesn't happen without --aot / --prod.

[filipesilva]

Can confirm this also happens on ng serve --aot. Looking into it.

[filipesilva]

Possibly related, but I can't see the issue fixed by it: #4009

[filipesilva]

I investigated a bit more and this doesn't seem to happen on all changes.

I can reproduce when changing a component template, but not when changing the component itself (changes are immediately reflected in this case).

So this seems related to the child compilers we use.

[ddehghan]

FYI - I might have had this same issue. Apparently I had another ng build process running in the background. when I killed that the issue got resolved.

[jd-carroll]

@filipesilva @bklik I am also experiencing this issue...
(My current workflow is to always CTRL+S twice)

I noticed on @bklik's version output that they are running node: 6.9.5. My local version of node is 6.9.5 and wondering if that could have anything to do with this?

Unfortunately, I can only installed "approved" versions of node at work 👎 so I cannot update my node at this time.