BrowserSync starts other project with an incremented port number

sage
1

October 28, 2018

Hi everybody!

Been using Sage for two years now and started to fiddle around with the new one half a year ago.
Right now I noticed a thing that doesn’t really make any sense to me. I’m also curious that may-be its not even my problem at all as a collegue of mine isn’t experiencing this.

The case is quite simple. I open a Sage 9 project, work on that, close it. Open another project that runs on Sage 9, start the server with yarn and the browsersync port number has changed from 3000 to 3001.

When I try to save files the browsersync doesn’t reload the site after that anymore. Basically a restart of the computer is needed to work on another project.

I’m using MAMP to run my WordPress installs. The confic.json settings are:
"publicPath": "/wp-content/themes/my-wp-theme", "devUrl": "http://localhost/my-wp-site", "proxyUrl": "http://localhost:3000", "cacheBusting": "[name]_[hash:8]", "watch": [ "app/**/*.php", "config/**/*.php", "resources/views/**/*.php" ]

So… what would be the case on this one?

2

Hi @r1987,

As a first step, can you make sure that when you close your first project it’s actually killing the node process running Browsersync? The fact that that the port increments when you run yarn start for the second project indicates that something is already listening on port 3000.