kokarn / atom-grunt-runner

Run Grunt tasks from Atom.
MIT License
31 stars 23 forks source link

Error loading gruntfile: Gruntfile not found #95

Open ghost opened 7 years ago

ghost commented 7 years ago

Tried multiple things; with/without root, forward/backslash, with/without .js ext and case sensitivity. Also tried npm install after removing the node_modules folder. The gruntfile tasks work OK through cmd.

I can confirm however the gruntfile is there. If I copy the path that it provides it resolves immediately.

grunt

Could it be a syntax issue or the way my gruntfile is composed?

kokarn commented 7 years ago

I think it's because it's not in the root of the project. Could you try to move it there?

If that doesn't help, please make sure it's not a duplicate of #10 or #20 :)

ghost commented 7 years ago

I've just copied it into the root, same issue. Tried those things listed in my initial post to no avail. Could there be a conflict with other packages perhaps?

atom-beautify / atom-jshint / file-icons / highlight-selected / linter / minimap / npm-install / simple-drag-drop-text

Wouldnt prepending the subfolder under Gruntfile Paths counter the root requirement?

kokarn commented 7 years ago

It would, in some cases. There's been quite a lot of discussion and fixes for the Gruntfile path and right now it's actually supported to not have it in root (#70).

I think the problem this time is with your actual path. Could you try to move it to a folder you can actually share? By the looks of it, it's mixing slashes (which shouldn't be a problem) but we've had issues with stuff like spaces before (which also should work).

ghost commented 7 years ago

Sorry! Cloned it to local now and I can actually share the whole thing. :-)

gruntatom

I left a copy of the gruntfile in the root for reference.

kokarn commented 7 years ago

Hmm, I see. Probably related to nesting but not really sure how and why. Might need to look through the code that finds Gruntfiles at some point...

freddyyeddy commented 4 years ago

Any fix for this yet?