Persistent javascript (angular) or cached client ?

[kvteal]

I'm currently developing an app with multiple angular clients and using Aspire to orchestrate them together with the backend and databases.

The issue me and my fellow developers are facing is that we often have to restart our aspire due to our dotnet projects using some libraries that do not properly work with hot-reload/watch. This is reasonable for all the dotnet projects, they start up fairly fast. However our clients always get build from scratch.

I'm wondering if there is a way to either keep the angular clients running between restarts or if we can use some caching to speed up the build process of the angular apps.
The initial thought of a persistent client feels the easiest one, but also the most inproper in the setup with aspire being able to dynamicly assign ports, have multiple instances, etc...
For caching we've looked at using a library like nx to bundle the angular app instead of the caching, but this is not as much a first citizen in the community toolkit and would require some javascript shenanigans to have it run as if it was just a regular angular app.
We could also move the entire startup of the clients outside the aspire setup and have aspire just handle the back-end, but this feels like a step back and undermining the 'single start-up script/program' which is why we switched to aspire.

I imagine alot of other people can find themselves running into this issue as well, and was wondering if there is a suggested approach to handling/reducing the pains or does everybody just live with the compile time each startup ?

[davidfowl]

You can use the rebuild command in the dashboard (assuming you are on aspire 13.2.x) instead of killing the entire apphost.