Open manifestinteractive opened 10 years ago
This typically means that grunt-runner can't require
your Gruntfile. Make sure you're Gruntfile is in the project root, and that you have opened your project in Atom at it's root.
grunt-runner will look for it at atom.project.getPath() + "/gruntfile"
So is it a problem if the file is named "Gruntfile.js" ? I do have the project open in the root.
On May 12, 2014, at 1:06 PM, Nicholas Clawson notifications@github.com wrote:
This typically means that grunt-runner can't require your Gruntfile. Make sure you're Gruntfile is in the project root, and that you have opened your project in Atom at it's root.
grunt-runner will look for it at atom.project.getPath() + "/gruntfile"
— Reply to this email directly or view it on GitHub.
It's worth a shot. It don't think it should matter if you're using Unix because I don't believe Unix is case sensitive. But try and let me know.
@manifestinteractive Were you able to resolve it? What was wrong?
i am seeing this also, just in starting up Atom 0.96.0 on Mac OS X 10.9.3 Mavericks. if you bring up the Developer Tools pane (cmd-alt.-i), you'll see this after launching Atom 0.96.0, even with no gruntfiles in a project being brought up —
grunt-runner: MODULE_NOT_FOUND grunt-runner-view.coffee:48
can anything be done about this? i was about to file a new issue when i saw this issue thread was all ready here. please advise.
best,
— faddah wolf portland, oregon, u.s.a. github.com/faddah
I am experiencing this same problem when opening a project without a grunt file.
That's intended. Just a little console.warn
.
@nickclaw ,
thank you for the response. it may be "intended," but it's confusing to see this warning message. maybe in future a way to check if a project is meant to have a grunt file and, if not, do not display the warning? my suggestion.
best,
— faddah wolf portland, oregon, u.s.a. https://github.com/faddah
I think I have the same problem as reported above. Is there any solution yet?
I was getting this error and was able to fix it by assigning my global grunt-cli in the settings for grunt-runner
: /usr/local/lib/node_modules/grunt-cli
.
Hope this also helps other.
Same error for me. MODULE_NOT_FOUND
I fixed this error using /usr/local/bin/
in Grunt Paths
PD: It doesn't works with open-last-project
package. It must close and reopen the project.
After trying different configurations a re-install of the package did it.
This happens everytime I launch a new atom session. I fix by running the command: Incompatible Packages: Reload Atom and Recheck Packages.
I had to rename Gruntfile.js to gruntfile.js for this to work, otherwise MODULE_NOT_FOUND
So it appears that there are many ways to get this. For me I can only open the folder that contains the gruntfile.js, If I open a folder further up the tree I get this error.
I have the same issue, but it's apparent (in my case) that it only happens when I load a new folder while grunt-runner already has been loaded.
I.e. running atom
from cli in a folder with a Gruntfile will work, but opening a blank Atom first, then changing the folder (to one that also have a Gruntfile) will not work. Doing View -> Reload
will fix the issue.
It seems grunt-runner needs to reinitialize each time a new folder/project is loaded.
Can confirm same step with @tdolsen to get this working. Ensuring a View -> Reload
will make it work 100% of the time.
I think this is related to #91 Can people try to updated to the latest published version and try again?
Thanks @eseceve Worked for me too!
I did not see this listed, but I have a a Gruntfile.js that runs fine in CLI but will not run with this package. I get the following error:
Error loading gruntfile: MODULE_NOT_FOUND
Below is the contents of the Gruntfile.js