Open Snugug opened 9 years ago
What are the plans for Libsass? Honestly was not following the recent development. Does Breakpoint, Singularity & Toolkit already support Libsass?
@iamcarrico I got aurora working with libsass, breakpoint, singularity, toolkit fairly easily by migrating to gulp-sass instead of compass and managing sass extensions with bower. Let me know how I can contribute this. Maybe an alternate subtheme?
I'm not quite sure what the best way to put LibSass in instead of Compass right now— but if we do I would rather use Eyeglass as it is built with node-sass in mind.
@iamcarrico https://github.com/dlmanning/gulp-sass is just a lightweight wrapper around node-sass and is used in tandem with eyeglass, but I understand the inclination to avoid bower and let NPM manage all packages, which is really the advantage of eyeglass. I'll take a look at how hard it would be to migrate to eyeglass.
The other important thing I'll check is how good the support is for breakpoint, singularity, and toolkit.
@iamcarrico https://github.com/sass-eyeglass/eyeglass/issues/64 is blocking meaningful eyeglass use with Gulp for the time being. tl;dr is top level @import
s resolve great with eyeglass, but @import
s within those extensions for example, breakpoint, don't resolve.
Things are very active though, so I'll try again soon.
Also, do you have any ideas about how best to patch the generator to support libsass? Compass seems assumed throughout the code. Last night I started down the path of making it an "extra" and forcing selection of gulp/bower, but _base.scss needs adaptation as well to import from bower, and config.rb, Gemfile, etc... still get created. Ideas?
I am p sure this has been resolved in the latest release.
And I would just alter the code to use LibSass, and we can do another major release. Remove all compass things.
Where's the Libsass love?