Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basset + live reload: new collections not being loaded by the view in the browser #211

Open
drbroad opened this issue Oct 10, 2013 · 0 comments

Comments

@drbroad
Copy link

drbroad commented Oct 10, 2013

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:

Basset::collection('UserStyles', function($collection)
{

    $directory = $collection->directory('assets/css', function($collection)
    {
        $collection->requireDirectory('less')->apply('Less');
        $collection->requireDirectory('sass')->apply('Sass');
        $collection->requireDirectory();
    });

    $directory->apply('CssMin');
    $directory->apply('UriRewriteFilter');
});

Would i be able to use ->rawOnEnvironment('local');, and if so what is the correct syntax?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant