Switching to grunt-sass for libsass / Susy .. error?

[Josh Vaughn]

Hi, your framework is really intriguing - you are running a lot of the stuff I've been learning and have been wanting to get all working together nicely. I downloaded a copy and got it running out of the box fine under Win8, the server popped up and displayed your intro page np ..

I need to run Susy 2.0 beta under grunt-sass/libsass because its super fast. So the first thing I did was try and hack it in to get it running :

$>bower install "susy#2.2.0.beta.3" .. at the command line, seemed to download fine .. then ..

$>npm install grunt-sass --save-dev .. again, seemed to install fine no issues .. however ..

$grunt --verbose .. gets me:

// [ .. all seemed good until .. ]

Running "bower:dev" (bower) task
Verifying property bower.dev exists in config...OK
Files: -> app/assets/components/

Reading S:\_base-frameworks\fireshell\src\components\normalize-css\normalize.css...OK
Writing app\assets\components\normalize-css.css...OK

S:\_base-frameworks\fireshell\src\components\normalize-css\normalize.css copied to.
Warning: Cannot call method 'split' of undefined Use --force to continue.

Aborted due to warnings.

The first thing that came to mind even before I tried this was that you have this in your Gruntfile:

/**
   * Dynamically load npm tasks
   */
  require('matchdep').filterDev('grunt-*').forEach(grunt.loadNpmTasks);

... which I am unfamiliar with, I was looking to delete the loadNpmTasks for grunt-contrib-sass and load grunt-sass instead -- I am thinking this is a conflict, can you help address this? Thanks!