Predictable LiveSync/HotReload

[valentinstoychev]

The main purpose of LiveSync (hot reload) is to enable faster development time and easier try/fail type of software development. This means that the ultimate/ideal solution will have the following characteristics:

• Will sync all the code (JS/CSS/XML and HTML) and assets (images and other non-code resources outside App_Resources) in fast time (under 1 sec). This means sync for all the operations -add/update/delete of assets/code.
  • Fast sync code (JS/CSS/XML)
  • Fast sync images Fast livesync of images #2277
• Logging/profiling/debugging experience should be the same as if no livesync is done

In 2.5 release(TBD) :

• Will display runtime errors in the app and will be able to recover from the error state without the need of restart/redeploy. Or if not possible in some cases it should be very VISIBLE for the user that he need to restart the livesync session.
• If it is not technically achievable to perform fast sync for a particular app change it will restart or even re-deploy the app if needed, but will not leave a change in the app skipped (not synchronized) with the target device (emulator or physical no matter)
  • Support plugin development when using the watch option Support plugin development when using the watch option #2276
  • Support symlinks in app and node modules folder Provision to watch files in symlinked directories for livesync command #2221

Not planned:

• Will work together with the debugger (see Support for Sync with watch nativescript-community/nativescript-vscode-extension#78)
• Fast sync for images? @tzraikov ?
• Will keep the app state Keep app state when sync changes #2814
• Working with AppBuilder and cloud-based emulators
• Plugins development should be able to be performed using livesync
• It should be possible to livesync multiple devices and OTA.

[sis0k0]

Most of the items are either implemented or obsolete in the context of {N} 4. Closing in favor of NativeScript/NativeScript#6398.