# enqueueCss doesn't work for yarn dev (but it does for yarn build)

**URL:** https://discourse.roots.io/t/enqueuecss-doesnt-work-for-yarn-dev-but-it-does-for-yarn-build/24212
**Category:** sage
**Tags:** bud, acorn, sage10
**Created:** 2022-11-09T21:44:22Z
**Posts:** 6

## Post 1 by @SergiArias — 2022-11-09T21:44:22Z

I have an extra css set up (without js) for woocommerce (woocommerce.css).  
In bud.config

```
.entry({
      app: ["@scripts/app", "@styles/app"],
      editor: ["@scripts/editor", "@styles/editor"],
      woocommerce: ["@styles/woocommerce"],
    })
```

Then, in setup.php:

```
add_action('wp_enqueue_scripts', function () {
    bundle('app')->enqueue();

    if (is_account_page() || is_cart() || is_checkout()) {
        bundle('woocommerce')->enqueueCss();
    }
}, 100);
```

If I use enqueue() it works apparently but generates a reload on Chrome because no woocommerce.js was found and thus loading the same app.js twice. If I use enqueueCss() it doesn’t work while yarn dev but it does work when yarn build.

I guess there is a bug in acorn and another one in bud.

---

## Post 2 by @ben — 2022-11-09T21:57:05Z

You should consider [refactoring your setup based on this comment about bundles](https://github.com/roots/bud/issues/1729#issuecomment-1264135718) from @kellymears

---

## Post 3 by @SergiArias — 2022-11-11T12:48:25Z

Probably it was an old bug. I ran composer update and updated bud too and now using enqueue() without caring if there is a js file or not works.

I was on Sage 10.2, updated to 10.3.1

---

## Post 4 by @tedw — 2023-09-14T13:35:32Z

FWIW I also had this issue previously but at some point this year the original bug seems to have been fixed because I can now use `enqueueCss()` without any issues locally. Now if I use `enqueue()` for bundles that don’t also have a JS file it breaks hot reloading locally. This makes sense, though, and isn’t a problem for me now that `enqueueCss()` is working.

---

## Post 5 by @tedw — 2023-10-31T19:23:23Z

`enqueueCss()` stopped working again for me locally. Anyone else have this issue? I’m using Bud 6.17.0 and Node 20.9.0.

---

## Post 6 by @tedw — 2023-10-31T19:56:03Z

I was able to fix it by switching back to `enqueue()` and adding `bud.runtime('single')` to my config. I previously had `bud.runtime(false)`.