Yarn start says successfully compiling but nothing at localhost:3000 and CSS not working

[knowler]

Do the changes ever show up? Are you on Windows? Is VirtualBox the hypervisor for Vagrant (VVV)? VBox is known to be slow on Windows if you are.

Confirm for me: accessing the website via the devUrl that you’ve specified in your config.json does bring you to the site (regardless of the state of the CSS). Also, confirm the same for localhost:3000.

Is just the CSS not working? Are there any Stylelint errors? Does running yarn lint:styles show any issues?

Is the publicPath shared above correct for your WordPress installation? You don’t happen to be doing anything with installing WordPress in a subdirectory or anything different.

Is your site being server with HTTPS? Is https:// in site_url or home?

When using yarn start you are only accessing the site from the proxyUrl, correct?

Sorry for all the questions. I’m just trying to pin point what is wrong as according to your config.json everything should work.

There’s a bunch of stuff I usually try when troubleshooting the build process that I’ve collected here:

Sage 9 browsersync not updating right

That’s really weird. Usually this issue is non-existent for me in Valet environments — in fact, I’ll use Valet to avoid it. The difficulty with this issue, is that it isn’t just one issue, but the similar output leads people to think it is. This makes troubleshooting on the forum troublesome as I can see people in this thread describe symptoms of a few different issues. I don’t know if it will help you, but here are my debugging steps for issues for this sort: Make sure your development URL …