Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Loading "Gruntfile.js" tasks...ERROR #3683

Closed
kevgithub opened this issue Oct 14, 2016 · 12 comments · Fixed by #3687
Closed

Loading "Gruntfile.js" tasks...ERROR #3683

kevgithub opened this issue Oct 14, 2016 · 12 comments · Fixed by #3687

Comments

@kevgithub
Copy link

screen shot 2016-10-14 at 16 31 09

I tried to install the "conventional-changelog" but still not work.

@gkatsev
Copy link
Member

gkatsev commented Oct 14, 2016

Are you running grunt from the build folder? You should be running it from the root of the project. I'm guessing that the issue is that shelljs-nodecli is not handling that correctly.

@kevgithub
Copy link
Author

Yes I ran it from the root

@misteroneill
Copy link
Member

Yes, shelljs-nodecli is not seeing binaries in node_modules/.bin. I'll see what I can do about fixing it.

@misteroneill
Copy link
Member

@kevgithub For the time being, if you npm install -g conventional-changelog-cli, the build will work.

@BernardoFBBraga
Copy link

@misteroneill I have the same issue but your suggestion did not work for me

@kevgithub did it work for you?

@BernardoFBBraga
Copy link

@misteroneill I copied the modifications from your commit #3687 and the grunt command now works (after running "npm install npm-run")
at the end it says it "Done, without errors", although I saw some stack traces so I don't feel very confident. Here is the output http://pastebin.com/F3KbARDz

@misteroneill
Copy link
Member

@BernardoFBBraga Thanks for checking.

That output looks like #3692 to me - I don't think there's a good solution to it at the moment. 😕

@gkatsev
Copy link
Member

gkatsev commented Oct 18, 2016

Yeah, the current solution is, unfortunately, to not use macos sierra (or remove the style generation from the build and use the pre-built styles).

gkatsev pushed a commit that referenced this issue Oct 18, 2016
shelljs-nodecli is having trouble getting the conventional-changelog package because the package name and binary name are different.

Fixes #3683
@BernardoFBBraga
Copy link

BernardoFBBraga commented Oct 18, 2016

@gkatsev I am running El Capitain 10.11.6
If you need any testing on my setup let me know

@gkatsev
Copy link
Member

gkatsev commented Oct 18, 2016

Oh, actually, you're right. I was too quick. Looks like your error isn't with sass but with fs-events. #3692 is a sass-related issue. I wonder what's up with fs-events.

@BernardoFBBraga what version of node and npm are you using?

@gkatsev
Copy link
Member

gkatsev commented Oct 19, 2016

Looks like it might be an issue with node 6.

@BernardoFBBraga
Copy link

BernardoFBBraga commented Oct 19, 2016

@gkatsev
npm version 3.10.8
node version 6.8.1
I tried uninstalling everything following this stackoverflow post : http://stackoverflow.com/questions/9283472/command-to-remove-all-npm-modules-globally

and then I followed the tutorial again, but the stacktrace still shows up. anyway to test if there are consequences?

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants