I suppose that’s the listener that tracks filesystem changes, and triggers the hot deploy. The fact that the hot deploy has been triggered does not mean that your specific changes are included in what is being hot-deployed. But for this you need an official response from the cuba team…
What I mean is that the ability to tweak the html/css/js of screens is something that is considered advanced (or exceptional) usage of the platform. For example, I tend to relegate that kind of code (custom js components, or similar things) in add-ons that are then simply “consumed” by target applications. In that regard, I never felt the need for hot-reload when developing such add-ons.
I don’t know if yours is a developer side use case (compile time), or a business/feature requirement (runtime).
That is, if the reloading of a dynamic or external JS file is part of your frontend business logic (at runtime), then there are several solutions to this, all of them outside the scope of this discussion (and not related to CUBA in any way).
If you refer to the compile time experience, that is hot reloading JS files that you change in the IDE, there’s no solution at the moment, or at least nothing that I’m aware of…