Ya this is starting to drive me a little crazy. This has been working on and off for me at this point. As of today, I have merged in all the changes from dev-master into my “base” theme and blade watching is working. I then merged my “base” theme into a forked theme I created, and it does not work. I have diff-ed the yarn.lock files and they are the same. I have diff-ed the assets/build directories and they are the same. Blew away node_modules, reinstalled, etc. All that is different is that my forked theme has different templates (using same base layout though), and has some leftover .php files that I am working on converting into blade templates.
I asked this before, but is there some way to get debug output from BrowserSync? I can see that my watch glob is being passed in (doing a console.log in the webpack.config.watch.js file), but I want to dump the actual file paths the glob is resolving.
I also should point out that disabling the HTML Injector does cause the page to reload when I save a file, so I’m assuming the watch detection is working. But I am still looking for some way of debugging and digging into this problem.