Live reload in remote ssh

[DerBahner]

Due to the way port forwarding probably works in BAS, the remote SSH extension does not allow for starting the app while enabling live reload. Because the live reload middleware is listening to the cloud forwarded ports e.g. port8080-workspaces[...].applications.cloud.sap, i.e. it thinks that this is localhost and is listening to the live-reload port on that adress. But starting (fiori run or ui5 serve) in local vs code while using remote SSH extension does not enable these ports. It must be a native feature of BAS. Could this be intregrated in some way?

[alex-gilin]

@DerBahner I must be missing something, so could you please include your scenario - what exactly is expected and what is not working, so we can reproduce the issue on our side.
but anyway, please make sure there is no warning sign in the top right corner of your VSCode terminal window, like in the attached screenshot. If so, please restart (or close and open a new one) the terminal before running the flow.

[DerBahner]

@alex-gilin Thanks for taking a look. I don't have any warnings in my terminal. The expected behavior is as follows:
I open VSC and connect to my dev space. This opens a new window with my BAS Dev space connected via remote ssh. Then I use the terminal in this new window to start the app with "npm start" (fiori run / ui5 serve). This starts my app normally. Now when I change code, there is no live reload, even though it is configured correctly. Expected behavior: Live reload works. I.e., when I change code in view/controller, it reloads the apps to reflect that there has been a code change.
Scenario 2:
I open my dev space in web browser. I run "npm start" there. My app starts normally. Now, any code changes made in the BAS Dev space trigger a live reload. Irrespective of whether I make them in the web browser or in the ssh remote window.