You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will preface this by saying it might not even be a basset issue - it could lie within live reload.
I am using: osx, sublime text 3, the live reload desktop app, the live reload chrome extension, laravel 4, basset 4.0.0
I have a vendor folder full of the bootstrap less files. This generally gets compiled once.
I have my own styles that are collected and minified upon each change.
These collections are added into my master blade template.
The problem is, whenever i update one of the css files live reload doesnt seem to know about the new build file of the css. It knows something happened - as you can see it polling. But all it does it reload the old build that the view in the browser currently refers to. You have to hard refresh/ run a build command from terminal to see any changes.
Is this an issue for anyone else?
I will preface this by saying it might not even be a basset issue - it could lie within live reload.
I am using: osx, sublime text 3, the live reload desktop app, the live reload chrome extension, laravel 4, basset 4.0.0
I have a vendor folder full of the bootstrap less files. This generally gets compiled once.
I have my own styles that are collected and minified upon each change.
These collections are added into my master blade template.
The problem is, whenever i update one of the css files live reload doesnt seem to know about the new build file of the css. It knows something happened - as you can see it polling. But all it does it reload the old build that the view in the browser currently refers to. You have to hard refresh/ run a build command from terminal to see any changes.
Is this an issue for anyone else?
My user styles collection:
Would i be able to use
->rawOnEnvironment('local');
, and if so what is the correct syntax?The text was updated successfully, but these errors were encountered: