Fatal error: Arguments to path.resolve must be strings #203

josephspens · 2015-03-31T20:33:43Z

grunt-sass v0.18.1
node-sass v2.1.1
node v0.12.0

I apologize if this is a duplicate issue and/or answered elsewhere, I checked around grunt-sass issues, node-sass issues, and grunt-notify without finding this error message discussed anywhere. Also I hope this is the place to report the issue and not node-sass.

When running grunt sass:prod

    Running "sass:prod" (sass) task
    Verifying property sass.prod exists in config...OK
    Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
    Files: src/main/webapp/media/styles/core.scss -> src/main/webapp/media/cache/core.css
    Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="compressed"
    Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="compressed"
    >> [grunt-notify] growl: growlnotify wasn't found. If you were hoping to use Growl, make you sure you have their command line script called Growlnotify. Mac: http://growl.info/downloads or Windows: http://www.growlforwindows.com/gfw/help/growlnotify.aspx and put it in your path. You should be able to type growlnotify --version and get something back.
    >> [grunt-notify] IS_WINDOWS: false
    >> [grunt-notify] PROGRAM_FILES: undefined
    >> [grunt-notify] PROGRAM_FILES_X86: undefined
    >> [grunt-notify] fullPathToApplication: false
    >> [grunt-notify] snarl: Snarl not available for this OS.
    >> [grunt-notify] os: Darwin
    >> [grunt-notify] version: 14.1.0
    >> [grunt-notify] IS_MAC: true
    >> [grunt-notify] MOUNTAIN_LION: true
    >> [grunt-notify] notification_center: Will use Notification Center
    >> [notification-center] cmd: /Users/joseph/Development/work-market/application/node_modules/grunt-notify/bin/Grunt.app/Contents/MacOS/Grunt
    >> [notification-center] args: -title backend sass:prod -message Arguments to path.resolve must be strings
    Fatal error: Arguments to path.resolve must be strings

Gruntfile:

sass: {
    options: {
        sourceMap: true,
        update: true,
        includePaths: ['<%= yeoman.components %>']
    },
    prod: {
        options: {
            style: 'compressed'
        },
        files: {
            '<%= yeoman.cache %>/app.css': '<%= yeoman.styles %>/app.scss',
            '<%= yeoman.cache %>/core.css': '<%= yeoman.styles %>/core.scss'
        }
    },
}

I've cleared out my node_modules, and reinstalled everything. I'm able to run the task if I downgrade to these versions:

grunt-sass v0.17.x
node-sass v1.x.x
node v0.10.36

I've instructed my team to not upgrade to node v0.12, however we're onboarding a lot of people and they're all downloading the latest package versions, so ideally we want our setup to work with node 0.12 out of the box.

The text was updated successfully, but these errors were encountered:

sindresorhus · 2015-04-03T02:26:09Z

Try the latest alpha and see if that solves it for you: #196 (comment)

josephspens · 2015-04-06T16:11:58Z

On node v0.12.0,
node-sass v3.0.0-beta.5,
grunt-sass 0.18.1

    Registering "grunt-sass" local Npm module tasks.
    Reading /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
    Parsing /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
    Loading "sass.js" tasks...ERROR
    >> Error: `libsass` bindings not found. Try reinstalling `node-sass`?
    >>     at getBinding (/Users/joseph/Development/work-market/application/node_modules/grunt-sass/node_modules/node-sass/lib/index.js:22:11)
    >>     at Object.<anonymous> (/Users/joseph/Development/work-market/application/node_modules/grunt-sass/node_modules/node-sass/lib/index.js:188:23)
    >>     at Module._compile (module.js:460:26)
    >>     at Object.Module._extensions..js (module.js:478:10)
    >>     at Module.load (module.js:355:32)
    >>     at Function.Module._load (module.js:310:12)
    >>     at Module.require (module.js:365:17)
    >>     at require (module.js:384:17)
    >>     at Object.<anonymous> (/Users/joseph/Development/work-market/application/node_modules/grunt-sass/tasks/sass.js:5:12)
    >>     at Module._compile (module.js:460:26)
    Initializing config...OK
    Loading "Gruntfile.js" tasks...OK
    + build, default, local, serve, test

    Running tasks: sass:dev
    >> [grunt-notify] growl: growlnotify wasn't found. If you were hoping to use Growl, make you sure you have their command line script called Growlnotify. Mac: http://growl.info/downloads or Windows: http://www.growlforwindows.com/gfw/help/growlnotify.aspx and put it in your path. You should be able to type growlnotify --version and get something back.
    >> [grunt-notify] IS_WINDOWS: false
    >> [grunt-notify] PROGRAM_FILES: undefined
    >> [grunt-notify] PROGRAM_FILES_X86: undefined
    >> [grunt-notify] fullPathToApplication: false
    >> [grunt-notify] snarl: Snarl not available for this OS.
    >> [grunt-notify] os: Darwin
    >> [grunt-notify] version: 14.1.0
    >> [grunt-notify] IS_MAC: true
    >> [grunt-notify] MOUNTAIN_LION: true
    >> [grunt-notify] notification_center: Will use Notification Center
    >> [notification-center] cmd: /Users/joseph/Development/work-market/application/node_modules/grunt-notify/bin/Grunt.app/Contents/MacOS/Grunt
    >> [notification-center] args: -title backend -message Task "sass:dev" not found.
    Warning: Task "sass:dev" not found. Use --force to continue.

    Aborted due to warnings.

I did an npm cache clean and install before doing this.

am11 · 2015-04-06T17:02:24Z

Hello,

Please make a gist for output of this:
https://gist.github.com/am11/9f429c211822a9b15aee replacing npm install node-sass with npm install node-sass@beta.

Also, which version of MacOS you are using?

//cc @xzyfer

josephspens · 2015-04-06T17:14:09Z

@am11 Thanks for responding, I'm running Yosemite
https://gist.github.com/josephspens/4eeb8176a669ff64f25b

2.3.0
v0.12.0
{ http_parser: '2.3',
  node: '0.12.0',
  v8: '3.28.73',
  uv: '1.0.2',
  zlib: '1.2.8',
  modules: '14',
  openssl: '1.0.1l' }
darwin
x64
/
> [email protected] install /Users/joseph/temp1/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /Users/joseph/temp1/node_modules/node-sass/vendor/darwin-x64-14/binding.node

> [email protected] postinstall /Users/joseph/temp1/node_modules/node-sass
> node scripts/build.js

` /Users/joseph/temp1/node_modules/node-sass/vendor/darwin-x64-14/binding.node ` exists. 
 testing binary.
Binary is fine; exiting.
[email protected] node_modules/node-sass
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
node-sass   3.0.0-beta.5    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.5    (Sass Compiler) [C/C++]
[eval]:1
console.log(require('node-sass').info())
                                 ^
TypeError: string is not a function
    at [eval]:1:34
    at Object.exports.runInThisContext (vm.js:74:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:460:26)
    at evalScript (node.js:431:25)
    at startup (node.js:90:7)
    at node.js:814:3
node-sass   3.0.0-beta.5    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.5    (Sass Compiler) [C/C++]
undefined
node-sass   3.0.0-beta.5    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.5    (Sass Compiler) [C/C++]
undefined

am11 · 2015-04-06T17:20:08Z

It seems it is working fine, when installed separately.

Now we need to figure out why it is throwing \libsass binding not found when install via grunt-sass.

Can you try installing grunt-sass alpha in ~/temp (isolated mode)?

josephspens · 2015-04-06T17:27:17Z

Not sure what isolated mode is... when installing grunt-sass (after running the script above, and without deleting the temp directory) I get this output

joseph-> npm install grunt-sass
|
> [email protected] install /Users/joseph/temp1/node_modules/grunt-sass/node_modules/node-sass
> node scripts/install.js


> [email protected] postinstall /Users/joseph/temp1/node_modules/grunt-sass/node_modules/node-sass
> node scripts/build.js

`darwin-x64-node-0.12` exists; testing
Binary is fine; exiting
[email protected] node_modules/grunt-sass
├── [email protected]
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])

am11 · 2015-04-06T17:31:07Z

Not sure what isolated mode is

I meant in temp directory by running npm install --save-dev sindresorhus/grunt-sass.

josephspens · 2015-04-06T17:50:13Z

Like this?

joseph-> npm cache clean && npm install --save-dev sindresorhus/grunt-sass
[email protected] node_modules/grunt-sass
├── [email protected]
└── [email protected] ([email protected], [email protected])

am11 · 2015-04-06T20:04:26Z

Yup.
I would give it a clean attempt (because you already installed node-sass@beta separately) like so:

cd /tmp
rm -rf node_modules
npm install --save-dev sindresorhus/grunt-sass

# now test with real code, if it is actually compiling files

If the above works, that naturally means both node-sass and grunt-sass are doing what they are supposed to do (i.e. working fine). :)

josephspens · 2015-04-06T21:07:44Z

I noticed I included node-sass in my project's package.json, so I removed that line + deleted my entire node_modules directory, ran npm install --save-dev sindresorhus/grunt-sass and npm install (to grab grunt and whatnot). After running grunt sass:dev -v I got the following output

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Bus error: 10

I googled around and apparently the solution to the bus error is to "upgrade" node to 0.10.22... obviously they're old threads.

Did you intend for me to build a new project to test the sass compilation in the tmp directory?

am11 · 2015-04-06T21:45:11Z

There are two issues you reported.

The first one (path.resolve) is a partly node-sass bug and partly "by design". I will fix the node-sass bug, but it will only stop emitting error and you will not get sourceMap in response because the pre-requisite of having source-map is to set outFile option (as mentioned in node-sass' readme). You can open this bug report in node-sass repo so it does not get forgotten. Besides, I am not sure why destination outFile is not set by grunt-sass in your case.

The second issue is installation; libsass binding not found. Sometimes it happens due to network issue or timeout/hungups (some external factor). Isolating the installation process renders a clear picture whether or not it is the issue with package. When node-sass installs, it downloads the prebuild binary (library; matching the description of your environment) separately, right after the npm finishes its install routine. If there is a network issue at that very instance, you will probably get that error. Apparently that is what happened when you first tried node-sass v3.0.0-beta.5.

am11 · 2015-04-06T22:03:46Z

Cross referencing sass/node-sass#839.

xzyfer · 2015-04-22T09:52:42Z

[email protected] has been released.

xzyfer · 2015-04-22T09:55:26Z

@josephspens please try the instructions from #203 (comment) and confirm the problem still exists.

josephspens · 2015-04-22T15:30:05Z

Sorry it took a minute, got swamped at work.

Here's the output after downloading the latest beta version:

mkdir: /Users/joseph/temp1: File exists
2.3.0
v0.12.0
{ http_parser: '2.3',
  node: '0.12.0',
  v8: '3.28.73',
  uv: '1.0.2',
  zlib: '1.2.8',
  modules: '14',
  openssl: '1.0.1l' }
darwin
x64
-
> [email protected] install /Users/joseph/temp1/node_modules/node-sass
> node scripts/install.js

Binary downloaded and installed at /Users/joseph/temp1/node_modules/node-sass/vendor/darwin-x64-14/binding.node

> [email protected] postinstall /Users/joseph/temp1/node_modules/node-sass
> node scripts/build.js

` /Users/joseph/temp1/node_modules/node-sass/vendor/darwin-x64-14/binding.node ` exists. 
 testing binary.
Binary is fine; exiting.
[email protected] node_modules/node-sass
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected])
├── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
├── [email protected] ([email protected], [email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected])
node-sass   3.0.0-beta.7    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.6    (Sass Compiler) [C/C++]
[eval]:1
console.log(require('node-sass').info())
                                 ^
TypeError: string is not a function
    at [eval]:1:34
    at Object.exports.runInThisContext (vm.js:74:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:460:26)
    at evalScript (node.js:431:25)
    at startup (node.js:90:7)
    at node.js:814:3
node-sass   3.0.0-beta.7    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.6    (Sass Compiler) [C/C++]
undefined
node-sass   3.0.0-beta.7    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.6    (Sass Compiler) [C/C++]
undefined

xzyfer · 2015-04-23T12:23:17Z

@josephspens due to an api change info is now an object not a function. That's what this error is telling you.

console.log(require('node-sass').info)

xzyfer · 2015-04-23T12:27:01Z

@josephspens the crux of this issue appears to be simply that you are using an incompatible version of node-sass. [email protected] is designed for [email protected]. If you need [email protected] you'll need to use master.

josephspens · 2015-04-23T15:22:47Z

I don't care what version of node-sass or grunt-sass I'm using, I just want this to work on node 0.12.

Which versions should I be using?
grunt-sass 0.17 and node-sass 2.x?

I want to point out that in this thread I was told to use node-sass 3.x, I was originally using node-sass 2.x

sindresorhus · 2015-04-23T16:11:58Z

#196 (comment)

josephspens · 2015-04-23T17:19:36Z

After reading the comment posted above, I decided to try using master branches for both node-sass and grunt-sass

node 0.12.0
grunt-sass 0.18.1 (master)
node-sass 3.0.0-beta.7 (master)

Running grunt sass:dev -v

Registering "grunt-sass" local Npm module tasks.
Reading /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
Parsing /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK

node-sass   3.0.0-beta.7    (Wrapper)   [JavaScript]
libsass     3.2.0-beta.6    (Sass Compiler) [C/C++]

Loading "sass.js" tasks...OK
+ sass
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, default, local, serve, test

Running tasks: sass:dev

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: src/main/webapp/media/styles/_config.scss -> src/main/webapp/media/cache/_config.css
Files: src/main/webapp/media/styles/_legacy.scss -> src/main/webapp/media/cache/_legacy.css
Files: src/main/webapp/media/styles/_states.scss -> src/main/webapp/media/cache/_states.css
Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
Files: src/main/webapp/media/styles/core.scss -> src/main/webapp/media/cache/core.css
Files: src/main/webapp/media/styles/wysiwyg.scss -> src/main/webapp/media/cache/wysiwyg.css
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Writing src/main/webapp/media/cache/wysiwyg.css...OK
Writing /Users/joseph/Development/work-market/application/src/main/webapp/media/cache/wysiwyg.css.map...OK
Bus error: 10

Tried again with latest release versions on node 0.12:

node 0.12.0
grunt-sass 0.18.1
node-sass 2.1.1

Running grunt sass:dev -v

Registering "grunt-sass" local Npm module tasks.
Reading /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
Parsing /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK

node-sass version: 2.1.1
libsass version: 3.1.0

Loading "sass.js" tasks...OK
+ sass
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, default, local, serve, test

Running tasks: sass:dev

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: src/main/webapp/media/styles/_config.scss -> src/main/webapp/media/cache/_config.css
Files: src/main/webapp/media/styles/_legacy.scss -> src/main/webapp/media/cache/_legacy.css
Files: src/main/webapp/media/styles/_states.scss -> src/main/webapp/media/cache/_states.css
Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
Files: src/main/webapp/media/styles/core.scss -> src/main/webapp/media/cache/core.css
Files: src/main/webapp/media/styles/wysiwyg.scss -> src/main/webapp/media/cache/wysiwyg.css
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Writing src/main/webapp/media/cache/wysiwyg.css...OK
Writing src/main/webapp/media/cache/wysiwyg.css.map...OK
>> [grunt-notify] growl: growlnotify wasn't found. If you were hoping to use Growl, make you sure you have their command line script called Growlnotify. Mac: http://growl.info/downloads or Windows: http://www.growlforwindows.com/gfw/help/growlnotify.aspx and put it in your path. You should be able to type growlnotify --version and get something back.
>> [grunt-notify] IS_WINDOWS: false
>> [grunt-notify] PROGRAM_FILES: undefined
>> [grunt-notify] PROGRAM_FILES_X86: undefined
>> [grunt-notify] fullPathToApplication: false
>> [grunt-notify] snarl: Snarl not available for this OS.
>> [grunt-notify] os: Darwin
>> [grunt-notify] version: 14.1.0
>> [grunt-notify] IS_MAC: true
>> [grunt-notify] MOUNTAIN_LION: true
>> [grunt-notify] notification_center: Will use Notification Center
>> [notification-center] cmd: /Users/joseph/Development/work-market/application/node_modules/grunt-notify/bin/Grunt.app/Contents/MacOS/Grunt
>> [notification-center] args: -title backend sass:dev -message Arguments to path.resolve must be strings
Fatal error: Arguments to path.resolve must be strings


Execution Time (2015-04-23 16:59:03 UTC)
loading tasks  258ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 63%
sass:dev       153ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 37%
Total 412ms

Same output using the same packages but downgrading to node 0.10.36:

node 0.10.36
grunt-sass 0.18.1
node-sass 2.1.1

Running grunt sass:dev -v

Registering "grunt-sass" local Npm module tasks.
Reading /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
Parsing /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK

node-sass version: 2.1.1
libsass version: 3.1.0

Loading "sass.js" tasks...OK
+ sass
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, default, local, serve, test

Running tasks: sass:dev

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: src/main/webapp/media/styles/_config.scss -> src/main/webapp/media/cache/_config.css
Files: src/main/webapp/media/styles/_legacy.scss -> src/main/webapp/media/cache/_legacy.css
Files: src/main/webapp/media/styles/_states.scss -> src/main/webapp/media/cache/_states.css
Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
Files: src/main/webapp/media/styles/core.scss -> src/main/webapp/media/cache/core.css
Files: src/main/webapp/media/styles/wysiwyg.scss -> src/main/webapp/media/cache/wysiwyg.css
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Writing src/main/webapp/media/cache/wysiwyg.css...OK
Writing src/main/webapp/media/cache/wysiwyg.css.map...OK
>> [grunt-notify] growl: growlnotify wasn't found. If you were hoping to use Growl, make you sure you have their command line script called Growlnotify. Mac: http://growl.info/downloads or Windows: http://www.growlforwindows.com/gfw/help/growlnotify.aspx and put it in your path. You should be able to type growlnotify --version and get something back.
>> [grunt-notify] IS_WINDOWS: false
>> [grunt-notify] PROGRAM_FILES: undefined
>> [grunt-notify] PROGRAM_FILES_X86: undefined
>> [grunt-notify] fullPathToApplication: false
>> [grunt-notify] snarl: Snarl not available for this OS.
>> [grunt-notify] os: Darwin
>> [grunt-notify] version: 14.1.0
>> [grunt-notify] IS_MAC: true
>> [grunt-notify] MOUNTAIN_LION: true
>> [grunt-notify] notification_center: Will use Notification Center
>> [notification-center] cmd: /Users/joseph/Development/work-market/application/node_modules/grunt-notify/bin/Grunt.app/Contents/MacOS/Grunt
>> [notification-center] args: -title backend sass:dev -message Arguments to path.resolve must be strings
Fatal error: Arguments to path.resolve must be strings


Execution Time (2015-04-23 17:01:49 UTC)
loading tasks  209ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 60%
sass:dev       141ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 40%
Total 351ms

And finally, using the configuration we have in production now, which works:

node 0.10.36
grunt-sass 0.18.1
node-sass 1.2.3

Running grunt sass:dev -v

Registering "grunt-sass" local Npm module tasks.
Reading /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
Parsing /Users/joseph/Development/work-market/application/node_modules/grunt-sass/package.json...OK
Loading "sass.js" tasks...OK
+ sass
Initializing config...OK
Loading "Gruntfile.js" tasks...OK
+ build, default, local, serve, test

Running tasks: sass:dev

Running "sass:dev" (sass) task
Verifying property sass.dev exists in config...OK
Files: src/main/webapp/media/styles/_config.scss -> src/main/webapp/media/cache/_config.css
Files: src/main/webapp/media/styles/_legacy.scss -> src/main/webapp/media/cache/_legacy.css
Files: src/main/webapp/media/styles/_states.scss -> src/main/webapp/media/cache/_states.css
Files: src/main/webapp/media/styles/app.scss -> src/main/webapp/media/cache/app.css
Files: src/main/webapp/media/styles/core.scss -> src/main/webapp/media/cache/core.css
Files: src/main/webapp/media/styles/wysiwyg.scss -> src/main/webapp/media/cache/wysiwyg.css
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Writing src/main/webapp/media/cache/app.css...OK
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
Writing src/main/webapp/media/cache/core.css...OK
Options: precision=10, sourceMap, update, includePaths=["src/main/webapp/media/bower_components"], style="expanded"
File src/main/webapp/media/cache/wysiwyg.css created.
File src/main/webapp/media/cache/wysiwyg.css.map created.
File src/main/webapp/media/cache/core.css created.
File src/main/webapp/media/cache/core.css.map created.
File src/main/webapp/media/cache/app.css created.
File src/main/webapp/media/cache/app.css.map created.

Done, without errors.


Execution Time (2015-04-23 17:07:07 UTC)
loading tasks  223ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 48%
sass:dev       243ms  ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 52%
Total 467ms

One last comment... my package.json file explicitly calls for grunt-sass 0.17.x, and it tries to download 0.17.0, however when I inspect the package.json in grunt-sass it says it's 0.18.1. This sounds like an issue with tagging, or maybe I'm missing something. I did an npm cache clean before installing and I'm still getting the mismatched versions.

joseph-> npm install
[email protected] node_modules/grunt-sass
├── [email protected]
├── [email protected] ([email protected], [email protected])
└── [email protected] ([email protected], [email protected], [email protected], [email protected], [email protected])

I want to thank everyone here for taking the time to help me with this... if this ends up being a dead end it's not the end of the world, it just means my team won't be able to upgrade node (or node-sass it seems). That may be a concern in the near future, but hopefully by then more versions of these packages will have been released for node 0.12 support.

am11 mentioned this issue Apr 6, 2015

Code: Skips path.resolve when outFile is not set sass/node-sass#839

Merged

xzyfer mentioned this issue Apr 20, 2015

Release 3.0.0-beta.6 sass/node-sass#873

Closed

8 tasks

sindresorhus closed this as completed Apr 23, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fatal error: Arguments to path.resolve must be strings #203

Fatal error: Arguments to path.resolve must be strings #203

josephspens commented Mar 31, 2015

sindresorhus commented Apr 3, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

am11 commented Apr 6, 2015

xzyfer commented Apr 22, 2015

xzyfer commented Apr 22, 2015

josephspens commented Apr 22, 2015

xzyfer commented Apr 23, 2015

xzyfer commented Apr 23, 2015

josephspens commented Apr 23, 2015

sindresorhus commented Apr 23, 2015

josephspens commented Apr 23, 2015

Fatal error: Arguments to path.resolve must be strings #203

Fatal error: Arguments to path.resolve must be strings #203

Comments

josephspens commented Mar 31, 2015

sindresorhus commented Apr 3, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

josephspens commented Apr 6, 2015

am11 commented Apr 6, 2015

am11 commented Apr 6, 2015

xzyfer commented Apr 22, 2015

xzyfer commented Apr 22, 2015

josephspens commented Apr 22, 2015

xzyfer commented Apr 23, 2015

xzyfer commented Apr 23, 2015

josephspens commented Apr 23, 2015

sindresorhus commented Apr 23, 2015

josephspens commented Apr 23, 2015