tvooo
commented
11 years ago Well, that is interesting indeed :) The fact that he gives you the list with tasks shows that Grunt was actually executed once (I use grunt to "expose" all available Grunt tasks). But the actual run of the Grunt command goes differently.
I discovered weird behavior regarding the PATH environment variable with ST2. How do you start ST?
Have a look at this question & answer: http://stackoverflow.com/questions/13033915/sublime-text-is-running-with-an-incorrect-path-environment-variable/19305760#19305760
Can you try to start ST via the command line and try again?
jdsimcoe
So I had the error about Grunt not being able to run because it could not exposes tasks. I am on OS X 10.9 and ST2 Build 2221. Friday the SublimeGrunt plugin worked splendidly installed via Package Control. Today I deleted the
~/tmp/folder because it was empty. I have Node 0.10.16 installed via Homebrew. I also have grunt-cli installed and grunt locally in my project folder with other dependencies. Grunt still runs flawlessly from the command line.I followed other advice in issues here and created the follow
SublimeGrunt.sublime-settings file:https://gist.github.com/7209234
When I run SublimeGrunt it brings up the activation menu and I select
default:https://www.dropbox.com/s/fh1vyblyzed08ud/Screenshot%202013-10-28%2021.37.31.png
The task gives the following error output in the console:
/bin/sh: grunt: command not foundI have recreated the
~/tmp/folder but it still doesn't work. What am I doing wrong?! Thanks for the help!