Re-compile does not always trigger browser update

[Ionaru]

OS?

Linux Kubuntu 16.10

Versions.

@angular/cli: 1.0.0-beta.30
node: 7.4.0
os: linux x64

Repro steps.

ng new newApp
cd newApp
ng serve
Edit app.component.ts (I changed 'app works!' to 'app works!!') and save.
This will trigger a re-compile.

The log given by the failure.

[WDS] App updated. Recompiling...
[WDS] App updated. Recompiling...
[WDS] Nothing changed.

Mention any other details that might be useful.

The hash between compile runs does not change.

I've seen an issue on this topic before, but it appears this is not a Windows-specific problem.

[biwin]

this happens for minor changes.

[vaags]

What kind of changes are considered to be "minor"?

[biwin]

may be adding/removing a semi colon. who knows!

[audgirka]

I am also facing this same issue on ubuntu 16.04.

When I try to add / remove a piece of code like (console.log() or a tag from html)

[eklee]

Also happens to me on Windows, for a new ng project, and an existing project that had been updated to 1.0.0-beta.30.

Changing a character in app.component.html triggers the browser update, but changing something in app.component.ts does not.

[klinki]

I'm facing the same problem. I will investigate it little bit further, but from what I observed, I can tell changing .ts triggers recompilation, BUT browser is still seeing old data.

[rgurgul]

I also have the same problem on Win 10.

[phil-cap]

Same here with Win7, node v6.9.1, npm v3.10.8

[jsBrian]

Same issue here: Win10 pro, Node.js v7.4.0, NPM v4.1.2.
When saving a .ts, the scripts compile, but:

• the package sizes don't seem to change
• the webapp doesn't refresh

For both my upgraded and new project.
Doesn't seem to matter if the change is small or big.

[jsBrian]

Tested, and v1.0.0-beta.29 doesn't seem to have the same issue for me.

[jsBrian]

I reinstalled beta 30, and I don't seem to have the issue anymore. :-\

[Brocco]

@Ionaru can you please re-test and report back? make sure you run npm cache clean before you reinstall your dependencies. I was trying to reproduce this locally on a clean install of beta 30 and was not able to reproduce.

Thanks!

[jwuliger]

FYI - To anyone who has not tried it yet. If you work directly from Master using npm link like shown in the README (at the bottom). It works, because the code for this has been fixed already. It can be a pain developing like that but I can always get through the NPM posted version error/bugs this way.

[MateEke]

We have the same issue on 3 Windows 10 machines with an existing project that had been updated to 1.0.0-beta.30 from 1.0.0-beta.26. All machines have Node 6.9.x.
One of the machines has a clean install of Windows, so no npm cache was present when the packages had been installed, it has 1.0.0-beta.30 from the beginning.