Gruntfile not found when dragging project folder into open window about atom-grunt-runner

[dwelle]

6.1 should solve this, but it's not yet up on apm (#26) so you have to update manually (download zip and replace in your packages folder)

Edit:

I take it back, it's still not solved.

It seems the atom.project.getPath() resolves to undefined upon plugins initialization (see source), for some reason, so it might be an Atom issue. Not sure if that is the prime reason, though, because it's undefined even when Atom is started via console - but the plugin correctly recognizes project's path.

Also, it's not an issue of Gruntfile.js not being found, it's the issue of Gruntfile.js being search for in a different folder - in this case in your Atom.exe folder (to which it falls back).

In any case, this is a duplicate of your prev issue #20

[cperryk]

I don't know much about developing these Atom plugins, but here's my theory after fiddling with the code for a few minutes: The plugin's initialization function, which caches the project path, runs when a new window is opened. If the user clicks on a file in the project directory or runs the "atom" command there, a window opens and the path is defined immediately. But when the user opens a blank new window, the path is not defined (how could it be? nothing is open). When the user drags a folder into the window or opens a project via the Project Manager extension, the project path is then defined, but Grunt Runner doesn't know this because it's not listening for the change.

So, basically, to get around this, Grunt Runner either needs to listen for changes to the project path or wait until the user attempts to use Grunt Runner to use the path (because it would be available then). For the latter approach, is it possible the package could just wait until the user tries to use the Run command to parse the gruntfile?

[ealves-pt]

Duplicate of #10. Several issues cause Error loading Gruntfile: gruntfile not found