livesync problems: only every other view/style file change triggers - node 8.9.4 and above on Mac at least

[NathanWalker]

@NickIliev created an issue repo here which exhibits the following livesync problems when using these node/npm versions:

Nathans-MacBook-Pro:issue-630 nathan$ node -v
v10.2.1
Nathans-MacBook-Pro:issue-630 nathan$ npm -v
6.4.0

Repro:

• clone repo here
• cd nativescript-dev-webpack/issue-630
• run project with: tns run ios --emulator --bundle --env.aot
• after it launches, just open items.component.html and change ActionBar title to something else and then save.
• console will show:

File change detected. Starting incremental webpack compilation...
Webpack compilation complete. Watching for file changes.
Webpack build done!

And nothing happens. Save again and it will livesync. Save again and it does same output but never reloads, continue/repeat and same cycle occurs.

[NickIliev]

Confirming this as a reproducible issue when using Node.js 10.x.x

Using the linked application on Windows with the followng versions

C:\Users\niliev>node -v
v10.10.0

C:\Users\niliev>npm -v
6.4.1

C:\Users\niliev>tns --version
4.2.3

The issue is not present with Node.js 8.9.4

Pressing Ctrl+S twice is needed for libvesynt to kick in - simply saving once will output the message below without actually syncing the changes.

File change detected. Starting incremental webpack compilation...
Webpack compilation complete. Watching for file changes.
Webpack build done!

[NathanWalker]

I can also confirm that Node.js 8.11.2 is also broken the same as described for 10 unfortunately.

[NathanWalker]

Unfortunately same issue is present in 8.9.4 on a Mac at least (macOS high sierra 10.13.6)

[davecoffin]

+1 guys, this is a real time killer, why was this put in the backlog?

[NickIliev]

The issue is in the backlog because the issue was triaged by the team and we are currently looking into it and will change its severity. By definition, a backlog is a list of features or technical tasks which the team maintains and which, at a given moment, are known to be necessary and sufficient to complete a project

Update: After some additional investigation it appears that the issue is reproducible with the --env.aot flag only. Removing the flag makes the livesync predictable. Using the flag reproduces the issue.