The team discussed the state of our LiveReload support in the context of #32111 and #43697. See the discussions there for more context.

We don't think that using the "livereload-js" library in any form (shaded, copied...) is the right answer. Also, it seems most front-end frameworks do ship their own solution to this problem anyway. We probably need to rethink the approach entirely here.

We would like revisit the entire "Developer Tools" arrangement in a future release, but we first need to properly assess the situation, the community's expectations and how the devtools module fits now in the modularized story. This is going to take some time and we will schedule this work in a future feature release, to be determined.

As a first step, we need to deprecate our LiveReload support for removal and give enough time to the community to move off of it, give feedback and consider other options.