This doesn't seem to be working with vs2013 update 2. When I access the context menu by right-clicking the gruntfile.js, I see the Grunt menu, but the only item in the list is 'Grunt' and then it complains that it can't find the task 'Grunt' when I run it. I know the gruntfile.js works because the grunt command-line works and finds all the tasks.
Thanks so much for this Paolo! One option that would be nice is the ability to mark some tasks as 'private' as it's common for some tasks to be created that are typically only executed as part of a bundle -- a build task that starts a series of tasks beginning with a directory clean is a good example. I don't really want to see 'gulp clean' in the list of available tasks, only 'gulp build'.
I have grunt-cli installed globally, and grunt installed in my projects npm directory. Grunt works fine on the command line but when using GruntLauncher I get the following message:
"'grunt' is not recognized as an internal or external command"
I'm running in Windows 8.1 with Visual Studio Premium V 12.0.21005.1 REL, NodeJS Tools 1.0 Alpha.
My installed Node version is 0.10.25.
Executing 'where grunt' produces:
Here are the steps I usually try:
1) Restart Visual Studio if you opened it before installing grunt. this might be it.
2) type: where grunt, at a command line and it should report a path to grunt.cmd (it does for you). If it didn't you could try and reinstall with: npm i -g grunt-cli. You could try and reinstall anyway.
3) Try manually adding the path to grunt.cmd (in your users AppData\Roaming\npm directory) to your System PATH environment variable.
4) Try logging off and back on again.
I have the same issue. Grunt is installed globally and I can execute it from anywhere in the system but not from Visual Studio. I am receiving
'grunt' is not recognized as an internal or external command,
operable program or batch file.
I generally use a "watch" task in my grunt setups and I noticed i could run it with your extension. It outputs everything to the Output window and runs as expected.
I also binded "npm install" and "npm update" into the build process of my solution. Then it actually fails to execute because of the running grunt watch task and files in use.
It would be nice the plugin checks for currently running tasks and either kills them automatically, or at least ask what to do, right when the (re)build starts.
Here's how my project is setup
1. Created a new "Project" from an Angular SPA App template
2. Directory looks like this -> "Solution/web" web being the project
3. Gruntfile.js is located in web/Gruntfile.js
I get an error when using the Grunt Launcher, nothing happens when I run a command :
Executing Grunt: test-unit
grunt-cli: The grunt command line interface. (v0.1.13)
I can get Grunt running separately in command line, why isn't this working? Am I doing something wrong?
Do you know what would be causing this? I'm running VS2013 update 4. When I load up my project and right-click on the gruntfile, I see "Grunt: cannot parse gruntfile". I know that my gruntfile works because it works with Grunt on the command-line.