I’ve found the culprit.
That gets at the heart of it - JS was broken and thus everything else was as well. The tricky thing for my brain was the JS was failing silently - no terminal errors, no console errors.
Trying again with Bud v6.24.0, once I realized that js wasn’t loading properly it led me to this discourse post regarding runtime chunks.
Temporarily setting bud.runtime(false) in my bud.config as indicated in that solution has everything running again - JS build, HMR, the whole shebang.
Definitely an oversight on my part, since this was flagged as a potentially breaking change in the 6.13.1 release. In my defense I think I missed it while reviewing the changes between 6.12.x and 6.24.x because for some reason 6.13 is missing from the releases menu over at https://bud.js.org/.
Since I’m not using Sage in this project I will look at how to update my wp_enqueue calls to use the runtime, as outlined in that post.
Many thanks @ben for taking a look, I really appreciate it!
