Ionic 6 proxy host/port conflict with default livereload endpoint

Developers configuring a custom proxy in Ionic 6 projects often encounter inconsistent livereload behavior when the proxy object includes host and port fields. The built-in livereload server defaults to port 35729, and redirecting this endpoint can prevent the client from establishing a connection, resulting in stale UI updates that require manual page refresh. This issue affects repeatable development environment setups where proxy rules are shared across teams or CI pipelines.

The precise configuration boundary at which livereload failure occurs remains unspecified, as does the extent to which operating-system-specific file-watching implementations influence the outcome. It is unclear whether the conflict stems from port collision, HTTP header negotiation, or path-based routing within the proxy middleware.

What configuration parameters of the proxy object in ionic.config.json directly trigger livereload disconnection in Ionic 6.x? Does the livereload client implement a fallback or reconnection strategy when the default endpoint is overridden? How can teams standardize proxy settings to maintain live-reload reliability across Windows and macOS development workflows?