When I do composer update I get a dependency error: Problem 1 - Installation request for classygeeks/potion 1.0.@dev -> satisfiable by cl assygeeks/potion[1.0.x-dev]. - classygeeks/potion 1.0.x-dev requires kriswallsmith/assetic 1.3.@dev -> n o matching package found.

Potential causes:

• A typo in the package name
• The package is not available in a stable-enough version according to your min imum-stability setting see https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion f or more details.

Read http://getcomposer.org/doc/articles/troubleshooting.md for further common problems.

Minor fix for passing the 'potion' only section of config to the commands instead of the entire config block Moderate fixed to the service provider to handle the deprecated call to createMatcher (which returns a regex version of the supplied pattern)

whenever i am making command php artisan potion:make-assets its saying the system canot find the path specified........ may be more docmentation is needed

Hi, I have this error when I try php artisan potion:make-assets The path is valid in my config file, so I wonder if the config file is properly loaded, or if it's even loaded, with Laravel 4.2.

Is there a reason why leafo/scssphp is locked to v0.1.1? I require some newer functionality available in the later versions.

Requiring a newer version of leafo/scss in my composer.json will revert potion to an earlier version (v.1.0.0) instead of v1.0.3 (obviously because that version of potion only suggests scssphp instead of requiring it).

I could do a PR, but I wanted to make sure that there wasn't some sort of underlying issue where we are required to use scssphp v0.1.1 instead of something more up-to-date.

Blade helper to output a list of compiled styles listStyles($withCacheBust = true)

listScripts - create a list of compiled scripts for insertion into page (footer, best practice)

Running php artisan potion:make-assets in Laravel 5 throws "Undefined index: assets_path" exception. As far as I see there is a problem in the PotionServiceProvider getConfig() method. Replacing

\Config::get("potion{$this->packageSeparator}config");

with

\Config::get("potion");

seems to fix the issue

Matt,

Love the package, but your leafo/scssphp dependency (0.1.) points to a really old version of leafo/scssphp that doesn't support @extend, causing the potion:make-assets command to break when it tries to process a SCSS file containing @extend. Updating the dependency to the more recent 0.6 fixes this issue.

Matt,

You've probably figured out by now that I'm using Potion on project and extending/modifying it to suit my needs. I know that not everyone will have the same needs I do, but I figured it would be better to submit each of my modifications as pull requests in case you decide some of them are worth integrating with your core project.

This one is a new potion configuration option called output_append

My Use Case

Sometimes, especially during development, I want to process multiple SCSS files into individual CSS files that are then included on different pages of my project individually. So, given the following file structure, I might have 3 pages on a project and each would individually want to include its own specific CSS.

/resources
    /assets
        /sass
            /pages
                page1.scss
                page2.scss
                page3.scss

The only way to do that with Potion right now is to setup three individual potions in the configuration, which grows tiresome as I add more pages to the project. Instead, I wanted to be able to have a single potion that would export sass/pages/*.scss to individual CSS files. Setting output = false gets me part of the way there, but the resulting files keep their exact file names, leading to .scss files, not .css files.

My solution: output_append.

This new, optional parameter may be set on any potion, and is simply concatenated to the end of the resulting asset. Thus the following potion is possible:

     //
    // Page-specific CSS
    [
        // Resources, relative paths to 'resource_path' above, can be any valid file or glob pattern
        'resources' => [
            '/sass/pages/*.scss',
        ],
        'filters' => [
            'css_import',
            'css_rewrite',
            'css_scssphp',
        ],
        'output'    => FALSE, // keep files separate
        'output_append' => '.css'
    ],

That would cause every scss file in /sass/pages to be processed into an individual file that would then have .css appended to the resulting asset name, which I could then include individually on any page of my project as required.

I ran into an issue where I incorrectly assumed the order of parameters between assetCss and the other asset helpers would be similar, but they weren't, so I moved the $rel argument to the end of the argument list so that $name and $version would be the first two arguments on all of the asset helpers. I recognize this would constitute a backwards-compatibility issue for those using Potion 1.x.

I also needed the ability to set the defer attribute on certain JS assets, so I added that optional argument to the assetJs helper.

The assetUrl method was not including a ? before the cache-busting v URL parameter, so I added that.

Lastly, and I know this is a style preference, I think the generated asset HTML tags would almost always be wanted on their own line, so I added a newline character to the HTML returned from each asset helper.

Incorrect dependencies for JSqueeze Incorrect namespacing of JSqueeze via the Assetic filter (\Patchwork\JSqueeze) Incorrect reference to JSqueeze Special Vars constant due to conflict in dependencies b/w Potion and Assetic

When using node, the excellent browserify package can be used to compile commonJS packages into one file. It would be great if potion would support this as well.

The PHP package https://github.com/mattcg/cjsDelivery supports compiling commonJS packges and could be used for this.

Is there a way you can make the artisan command watch for changes then make the assets? Like this http://symfony.com/doc/current/cookbook/assetic/asset_management.html#dumping-asset-files ?