# HMR issues after upgrading Bud to 6.24.0

**URL:** https://discourse.roots.io/t/hmr-issues-after-upgrading-bud-to-6-24-0/29290
**Category:** bud
**Created:** 2025-02-22T01:01:39Z
**Posts:** 9
**Showing post:** 8 of 9

## Post 8 by @needle — 2025-02-25T21:44:20Z

I’ve found the culprit.

> [@ben](#):
>
> The dev server never compiles a CSS file, it’s injected via JS

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](https://discourse.roots.io/t/bud-compiled-js-different-after-updating-to-6-14-3/25767) 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/](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!

 ![Screenshot 2025-02-25 at 1.15.44 PM](https://discourse.roots.io/uploads/default/original/2X/c/c9b3823357f8ba6621cb9dac894106ebc30c03cf.png)

---

_[View the full topic](https://discourse.roots.io/t/hmr-issues-after-upgrading-bud-to-6-24-0/29290)._