Running causes devtools to open. about atom-grunt-runner HOT 13 CLOSED

Which version are you running? Are there any errors shown in the console?

from atom-grunt-runner.

0.5.1

Uncaught Error: spawn ENOENT events.js:82
exports._errnoException util.js:682
ChildProcess._handle.onexit child_process.js:857
(anonymous function) child_process.js:1005
_tickCallback

I tried setting the path, alas.

from atom-grunt-runner.

Make sure you have grunt-cli installed globally. Then run which grunt in the command line and use whatever it outputs as the path. For example my output is /Users/nickclaw/local/bin/grunt so I would put /Users/nickclaw/local/bin in the path settings.

from atom-grunt-runner.

I'm running v0.5.1 too and have the same error thrown in the console. When I set the path to my global grunt binary /usr/local/bin/grunt I get the error 'could not find grunt command' in the grunt-runner log pane.

from atom-grunt-runner.

Ah, just saw the solution in #3: drop grunt from the path setting.

from atom-grunt-runner.

I had this same problem, for the same reason. It would be nice if it detected grunt at the end of the path and knew what it meant.

from atom-grunt-runner.

+1 @alexlafroscia. I also had this issue.

from atom-grunt-runner.

Did try your solutions... didn't worked out. Still get the same error.

from atom-grunt-runner.

Same here, grunt is installed in ~/.nvm/versions/node/v0.12.2/bin

Specifying ~/.nvm/versions/node/v0.12.2/bin or /Users/username/.nvm/versions/node/v0.12.2/bin in the PATH settings still doesn't allow grunt-runner to find grunt.

from atom-grunt-runner.

Same here. Grunt is installed /usr/local/bin/ but this no worky.

from atom-grunt-runner.

Are you getting some error or are devtools opening?

Recently I had the problem with Atom having different paths depending on how you open it.

There is a big thread about that over here steelbrain/linter#150 but the solution for me and some others was to add all the paths from $PATH to init.coffee.

This is now my init.coffee

# Your init script
#
# Atom will evaluate this file each time a new window is opened. It is run
# after packages are loaded/activated and after the previous editor state
# has been restored.
#
# An example hack to make opened Markdown files always be soft wrapped:
#
# path = require 'path'
#
# atom.workspaceView.eachEditorView (editorView) ->
#   editor = editorView.getEditor()
#   if path.extname(editor.getPath()) is '.md'
#     editor.setSoftWrap(true)

process.env.PATH = [
        '/usr/local/bin',
        '/usr/bin'
        '/bin',
        '/usr/sbin',
        '/sbin'
    ].join( ':' );

from atom-grunt-runner.

@kokarn Running Atom via the command line does indeed fix the problem.

from atom-grunt-runner.

I'll pitch in that @kokarn's workaround fixed it for me (so far only tested after launching via the command line). Edit: I've launched both via the command line and by opening Atom directly and have had no issues.

from atom-grunt-runner.