Maybe I'm doing it wrong, but I'm trying to edit scss and blade templates and at certain points in the process I'm coming to a dead end where the changes aren't being reflected.
I'm using; npm run watch
I've tried all the cache, view and config clear artisan commands and the changes still don't manifest. I went to make a brew, come back, press refresh and suddenly the changes are there! Is it my browser (chrome), is it laravel... or is it something I'm (not) doing?
I'm thinking it's my browser because there's no errors on laravel that I can see, but I'm hoping you seasoned veterans have come across this issue before and know what I'm experiencing and how to avoid/fix it in future as I'm not experienced enough to notice before I've already gone down the rabbit hole of making further changes.
It's probably the browser yes, there are many things it can be, but #1 is the browser. (then the apache / nginx settings, then disk caching)
You can try to disable Chrome's cache by going to the developer toolbar ( F12 ), go into settings ( F1 ), Scroll down to "Network", and check the box for "Disable Cache (while DevTools is open)"
One way around this is to use versioning on your assets in mix.
https://laravel.com/docs/5.6/mix#versioning-and-cache-busting
Then every time you compile your assets, it will force the browser to download the newest version. If the asset hasn't changed, it will use the asset from the browsers cache (or download it if it isn't in cache)
I'd highly suggest using the cache-busting that mix offers, or your users will have the same problems you are, and you really don't want to have to explain to them to force-refresh the browser or clear their cache. It should just use the newest version of the assets all the time.
Please or to participate in this conversation.