# 'yarn dev' not: (1) rebuilding css changes, (2) reloading changes in browser

**URL:** https://discourse.roots.io/t/yarn-dev-not-1-rebuilding-css-changes-2-reloading-changes-in-browser/25348
**Category:** sage
**Tags:** sage10
**Created:** 2023-05-15T21:52:09Z
**Posts:** 5
**Showing post:** 2 of 5

## Post 2 by @strarsis — 2023-05-18T14:38:27Z

One reason that comes to mind is that the source files are mounted into Vagrant in a way that does not allow for file notifications.  
Also take a look at the new Lima feature in recent Trellis:

> [@Introducing Lima to Trellis for Faster Local Development](https://discourse.roots.io/t/introducing-lima-to-trellis-for-faster-local-development/24928):
>
> We’ve added experimental support for Lima to Trellis, which allows us to drop VirtualBox/Parallels and Vagrant for faster local dev environments. Read more on our blog: [Introducing Lima to Trellis for Faster Local Development | Roots](https://roots.io/introducing-lima-to-trellis-for-faster-local-development/)

---

_[View the full topic](https://discourse.roots.io/t/yarn-dev-not-1-rebuilding-css-changes-2-reloading-changes-in-browser/25348)._