Fatal Error Reported Using grunt-sass Version 1.1.0

[tlattimore]

When following Grunt integration I am getting this error reported:

Fatal error: Arguments to path.resolve must be strings

Steps to reproduce:

Add the following to your package.json

{
  "devDependencies": {
    "eyeglass": "0.6.3",
    "grunt": "0.4.5",
    "grunt-sass": "1.1.0"
  }
}

Create a file named Gruntfile.js that contains this:

'use strict';

var eyeglass = require("eyeglass");

module.exports = function(grunt) {
    grunt.initConfig({
        watch: {
            sass: {
                files: ['*.{scss,sass}', 'Gruntfile.js'],
                tasks: ['sass:dist']
            },
        },
    sass: {
      options: require("eyeglass").decorate({
        sourceMap: true
      }),
      dist: {
        files: {
          'style.css': 'style.scss'
        }
      }
    }
    });
    grunt.registerTask('default', ['sass:dist']);
    grunt.loadNpmTasks('grunt-sass');
};

Create a file named style.scss with the following:

.title {
    content: 'Eyeglass is Awesome!';
}

Than run:

grunt

[eoneill]

What versions of things are you using?

I was able to successfully run your code with the following:

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

[tlattimore]

Sorry, @eoneill. I should have my package.json to this.

I was running grunt-sass version 1.1.0 but when I roll back to 1.0.0 I can no longer replicate this error and eyeglass appears to be working correctly. I will update the issue description to reflect this.

I am not sure if this should be left open, or whether it is an issue that should be filed against grunt-sass?

[eoneill]

Ah, I missed that part in your initial report. The issue is probably that [email protected] is using node-sass@^3.4.0. Unfortunately, 3.4.0 (and 3.4.1) contain a breaking change that prevents eyeglass from working correctly: sass/node-sass#1220

The good news, this should be fixed in [email protected] in the next few days. Until then, use [email protected]. I'll keep this ticket open until 3.4.2 lands, at which point [email protected] should work.

[tlattimore]

Thanks for clarifying this, @eoneill! 👍

[eoneill]

resolved with [email protected] and [email protected]