Grunt on Windows 8: 'grunt' is not recogni

Question

I'm having a problem running Grunt from the command line on my Windows 8 machine.

My research indicates the most common solution is to install grunt-cli, since Grunt is no longer global. I also need to make sure I actually install the Grunt task runner, since that's not installed with grunt-cli.

Other solutions point to the PATH system environment variable, but that appears to be pointed as I'd expect to:

C:\Users[username]\AppData\Roaming\npm

Having done all that, I'm still getting a "'grunt' is not recognized as an internal or external command, operable program or batch file" error message in the CLI. I've tried the following things, uninstalling everything after every attempt:

• Installed grunt-cli globally (npm install -g grunt-cli), then grunt at the directory level I want to use it (npm install grunt)
• The same as above, but with the order of installation reversed
• The same as both of the above, but using the Admin Command Prompt

Am I missing something obvious?

Answer 1

I have stucked with problem on Windows 8, that after install grunt-cli I've always got "command not found" while I'm tried to check grunt -v or where grunt. So I've added to enviroment PATH this path C:\Program Files (x86)\Git\local and run grunt.cmd from that folder (you need to look in node_modules folder here). And after reloading my terminal everything started to work.

Answer 2

I've not had any issues with grunt on several different windows 8 machines.

If you open the folder: C:\Users\[username]\AppData\Roaming\npm

Do you have a file named grunt.cmd in this folder?

If not I'd maybe try npm install -g grunt-cli again, maybe from an elevated command prompt.

If this exists and you have C:\Users\[username]\AppData\Roaming\npm in your PATH environment variable then typing grunt from a command prompt should work.

Silly question, have you tried closing the command prompt and opening a new one?

Answer 3

some times NPM install corrupts the basic windows path. i usually have a copy of my own version of PATH mainted separately. every week or on some installs i manually configure and update the %PATH% variable.

Basically Grunt.cmd is not availbe through %PATH% variable.

Answer 4

I was facing the same problem on windows 8

I have added ' %APPDATA%\npm ' to the path variable . It has been working fine.

Answer 5

Confirm your PATH is correct (and not messed up). Just type PATH from the command prompt. There's really no other explanation that makes sense given the error you're describing and the steps you've taken.

Normally, using the where grunt command would have found grunt.cmd in your path if npm is installed correctly and it has been properly added to the system path.

Answer 6

Same happened to me and here was the solution: Have you got 2 different versions of Node.JS installed? Maybe Nodist? This means you likely got NPM installed twice which will install the commands into 2 different folders: Once into C:\Users\<user>\AppData\Roaming\npm and once into C:\dev\nodist\bin\bin.

C:\dev\nodist\bin\bin wasn't on my path variable so I added it, and I removed the Node.JS version I didn't want to use.