# My browsersync is gonna give me a seizure

**URL:** https://discourse.roots.io/t/my-browsersync-is-gonna-give-me-a-seizure/12263
**Category:** sage
**Tags:** browsersync, webpack, sage9
**Created:** 2018-04-19T18:42:39Z
**Posts:** 9

## Post 1 by @Jacob_Morris — 2018-04-19T18:42:40Z

![Peek%202018-04-19%2014-40](https://discourse.roots.io/uploads/default/original/2X/1/11d415ccc6de523fac11d6633e6fafc93113f111.gif)

so basically every time I save a non-scss change, this is how browsersync loads up the changes. I didn’t do anything fancy, all very basic stuff.

Any idea what could be causing this issue?

Running Ubuntu 17.04

---

## Post 2 by @strarsis — 2018-04-19T19:11:01Z

Looks like the SVG (logo) is constrained only by the stylesheet… Giving it an explicit initial size using `width` and `height` attributes on it or adding it as a CSS background could help with this kind of issue.

---

## Post 3 by @Jacob_Morris — 2018-04-19T19:16:48Z

That didn’t seem to work, so I removed the logo completely and the issue remains.

---

## Post 4 by @knowler — 2018-04-19T19:31:36Z

Is your `publicPath` set correctly?

> <https://github.com/roots/sage/blob/master/resources/assets/config.json#L11>

---

## Post 5 by @Jacob_Morris — 2018-04-19T19:36:21Z

Mine is looking identical, minus the theme name/url

```
{
  "entry": {
    "main": [
      "./scripts/main.js",
      "./styles/main.scss"
    ],
    "customizer": [
      "./scripts/customizer.js"
    ]
  },
  "publicPath": "/app/themes/Bushman",
  "devUrl": "http://bushman.test",
  "proxyUrl": "http://localhost:3000",
  "cacheBusting": "[name]_[hash:8]",
  "watch": [
    "app/**/*.php",
    "config/**/*.php",
    "resources/views/**/*.php"
  ]
}
```

---

## Post 6 by @knowler — 2018-04-19T19:38:36Z

And you’re running in a Bedrock setup? Are you using Trellis/Vagrant for your local dev environment? Or Valet? Or something else?

---

## Post 7 by @Jacob_Morris — 2018-04-19T19:48:00Z

Yes, it is bedrock, with sage theme, and I am using homestead as my env. I’ve been using regular gulp for about a year now with homestead and never had anything like this come up.

---

## Post 8 by @knowler — 2018-04-19T20:29:31Z

Ok, and you are running the build process (`yarn start`) from your local machine, not the Homestead VM, correct?

---

## Post 9 by @ben — 2018-04-20T02:28:11Z

When you do `yarn start` and the BS session starts, is it actually running on `http://localhost:3000`, or do you have a port conflict and it’s running on some other port?

If it’s not running on port `3000`, [try killing whatever is on there](https://discourse.roots.io/t/xmlhttprequest-cannot-load-hot-update-json-due-to-access-control-checks/12145/5?u=benword) …or try updating the config with a different port