johnjenkins
commented
9 years ago Just another thought - per project I use a Gemfile with particular gem versions (of compass, sass etc) - just wondering if perhaps sublime-grunt was trying to use global gems which are perhaps not compatible? Or something like that anyway.
tvooo
Hi there, thanks for a great project - I'm really on board with this. Apologies if any of the following is nonsense - I don't really know what I'm talking about.
Everything seems in working order, except I can't get the Compass task to work (obviously works fine in terminal). I'm on Mac Yosemite.
The error message is suitably vague:
Warning: .../node_modules/grunt-contrib-compass/node_modules/tmp/lib/tmp.js:261 throw err; ^ Error: spawn ENOENT at errnoException (child_process.js:1011:11) at Process.ChildProcess._handle.onexit (child_process.js:802:34) Use --force to continue.
A quick search of this leads to suggestions of updates of compass/ruby. I already have this set-up using rvm - cmd uses Ruby version 2.1.1 by default. This led me to think, perhaps sublime-grunt was using the global/system Ruby version? I've tried opening Sublime using cmd but this didn't help, any other ideas?
Failing that, I wondered if I could run a grunt task with a verbose flag to see if there was any other information that could be gleamed?
Once again, thanks so much for your work on this,
John