<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">This is *awesome*, thanks for your work!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 12, 2018, at 9:13 AM, Nicholas Alexander <<a href="mailto:nalexander@mozilla.com" class="">nalexander@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hello Firefox front-end developers!</div><div class=""><br class=""></div><div class="">Long before Austin, Brian Grinstead and I did some work on improving the Firefox front-end developer workflow. We started with a lightweight filesystem watcher called |mach watch| to incrementally run |mach build faster|.</div><div class=""><br class=""><div class="">The first bits of that work landed [1] [2] but there were some issues around purging startup caches [3] [4] that prevented us publicizing it widely. I think I've addressed those issues now, so we're ready for wider usage!</div></div><div class=""><br class=""></div><div class="">Bare-bones instructions are at<br class=""></div><div class=""><br class=""></div><div class=""><a href="https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Incremental_builds_with_filesystem_watching" class="">https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Incremental_builds_with_filesystem_watching</a></div><div class=""><br class=""></div><div class=""><div class="">Basically, run |mach watch| in one terminal, run |mach run| in
another, and use the Quick Restart hot-key to test your editor changes
quickly.<br class=""></div><div class=""><br class=""></div></div><div class="">I'm currently working on incorporating |mach watch| into |mach run| and adding a Web Socket server to |mach watch| [5]. That will let us immediately refresh browser CSS in a running browser, and also allow us to reload in-content pages like about: pages. This functionality will mimic the webpack watcher (but does not use any of the same implementation, sadly).</div><div class=""><br class=""></div><div class="">After that, the sky is the limit: anything you might like to do with a bidirectional communication channel between the build system and development environment, and the browser under development, could be possible.<br class=""></div><div class=""><br class=""></div><div class="">Thanks to Brian for browser integration, and to Dave Townsend and Myk Melez for helpful conversations; to many in the Firefox front-end team and devtools team for early feedback; and to Greg Szorc for reviewing build system patches.</div><div class=""><br class=""></div><div class="">Best,</div><div class="">Nick<br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1384241" class="">https://bugzilla.mozilla.org/show_bug.cgi?id=1384241</a></div><div class="">[2] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1385452" class="">https://bugzilla.mozilla.org/show_bug.cgi?id=1385452</a><br class=""></div><div class="">[3] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1386040" class="">https://bugzilla.mozilla.org/show_bug.cgi?id=1386040</a></div><div class="">[4] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1368699" class="">https://bugzilla.mozilla.org/show_bug.cgi?id=1368699</a></div><div class="">[5] <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1388899" class="">https://bugzilla.mozilla.org/show_bug.cgi?id=1388899</a><br class=""></div></div>
_______________________________________________<br class="">firefox-dev mailing list<br class=""><a href="mailto:firefox-dev@mozilla.org" class="">firefox-dev@mozilla.org</a><br class="">https://mail.mozilla.org/listinfo/firefox-dev<br class=""></div></blockquote></div><br class=""></body></html>