Is the --gruntfile option broken in grunt-cli 0.1.9 ?

[pixelzoom]

I upgraded from grunt-cli 0.1.6 to 0.1.9, using 'npm install -g grunt-cli'

% npm --version
1.3.4
% grunt --version
grunt-cli v0.1.9
grunt v0.4.1
%

Our build process uses a Gruntfile.js that is shared by multiple projects, so we use the --gruntfile option when invoking grunt. Here's what happens after updating grunt-cli:

% grunt --gruntfile ../Gruntfile.js
grunt-cli: The grunt command line interface. (v0.1.9)

Fatal error: Unable to find local grunt.

If you're seeing this message, either a Gruntfile wasn't found or grunt
hasn't been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

http://gruntjs.com/getting-started
grunt failed
%

'npm ls' shows that I have a local grunt installed (grunt@0.4.1).

If I copy Gruntfile.js to the current directory and run 'grunt', everything is fine. This is part of a build process that has been working smoothly for quite some time, and we've made no changes to that build process other than to update grunt-cli.

[pixelzoom]

Reverting to grunt-cli 0.1.8 fixes the problem: sudo npm install -g grunt-cli@0.1.8

So this would appear to be something that was introduced in 0.1.9.

[samreid]

I'm having the same problem. Here is my version information:

Windows 8 x64
$ npm --version
1.3.2

$ grunt --version
grunt-cli v0.1.9
grunt v0.4.1

[jarrodpayne]

Could this have anything to do with:

If youre seeing this message, either a Gruntfile wasnt found or 'grunt
hasnt been installed locally to your project'. For more information about
installing and configuring grunt, please see the Getting Started guide:

You say that you have installed it globally.

[pixelzoom]

Please re-read the original report. I indicated that I installed grunt-cli globally and grunt locally, as recommended by the grunt installation instructions. The grunt-cli is installed globally in /usr/local/bin/grunt. And grunt is installed locally, as verified by 'npm ls | grep grunt'.

[pixelzoom]

The complete steps I followed to install grunt-cli globally and grunt locally, and the resulting error.

% sudo npm install -g grunt-cli
% grunt --version
grunt-cli v0.1.9
grunt v0.4.1
% cd my-project
% cat package.json
{
  "name": "my-project",
  "version": "0.0.0-1",
  "license": "GPLv3",
  "devDependencies": {
    "grunt": "~0.4.1",
    "grunt-requirejs": "~0.3.2",
    "grunt-contrib-jshint": "~0.5.4"
  }
}
% npm install
% npm ls | grep grunt
├─┬ grunt@0.4.1
├─┬ grunt-contrib-jshint@0.5.4
└─┬ grunt-requirejs@0.3.5
  ├─┬ grunt-backbonebuilder@0.1.4
  │ └─┬ grunt@0.3.17
  ├─┬ grunt-jquerybuilder@0.1.4
  │ ├─┬ grunt-contrib-jshint@0.1.1
  │ ├─┬ grunt-contrib-nodeunit@0.1.2
  │ ├─┬ grunt-contrib-watch@0.2.0
  ├─┬ grunt-lodashbuilder@0.1.7
  │ ├─┬ grunt-contrib-jshint@0.1.1
  │ ├─┬ grunt-contrib-nodeunit@0.1.2
  │ ├─┬ grunt-contrib-watch@0.2.0
% grunt --gruntfile ../chipper/grunt/Gruntfile.js
grunt-cli: The grunt command line interface. (v0.1.9)

Fatal error: Unable to find local grunt.

If you're seeing this message, either a Gruntfile wasn't found or grunt
hasn't been installed locally to your project. For more information about
installing and configuring grunt, please see the Getting Started guide:

http://gruntjs.com/getting-started
grunt failed
%

[jarrodpayne]

My apologies. I, too am running into this issue now. I had some tasks that were using the Gruntfile.js rather than my altGruntfile.js. So, I removed Gruntfile.js and boom... Fatal error: Unable to find Gruntfile. Even though, I am trying to run this grunt build --gruntfile altGruntfile.js.

I tried sudo npm install -g grunt-cli@0.1.8, but still receive the same error.

$ grunt --version
grunt-cli v0.1.8
grunt v0.4.1

@pixelzoom Did you do anything other than revert to grunt-cli v0.1.8 to get this working?

[pixelzoom]

The only thing I did to workaround this was to revert to the previous version of grunt-cli:

sudo npm install -g grunt-cli@0.1.8

[pixelzoom]

Actually... I might have reverted to 0.1.6 first, because that's the version I had before updating. Then I updated to 0.1.8.

[jarrodpayne]

Would you happen to be running grunt-concurrent?

If so, please see my issue here: sindresorhus/grunt-concurrent#17

Perhaps this is affecting more than just grunt-concurrent.

[pixelzoom]

I'm not intentionally using grunt-concurrent. How can I confirm?

[jarrodpayne]

Look in package.json. Also check in Gruntfile for 'concurrent'. My problems was the fact that I was using the --gruntfile argument while using a grunt plugin that didn't properly support passing those arguments around. See my issue sindresorhus/grunt-concurrent#17

Your issue doesn't seem to be the same because a downgrade worked for you, while that didn't work for me. But, just check to see if you are running any tasks that might have the same issue.

[pixelzoom]

Complete package.json was provided above. No 'concurrent' in Gruntfile.

[pixelzoom]

The only tasks I'm running in Gruntfile are these:

grunt.loadNpmTasks( 'grunt-requirejs' );
grunt.loadNpmTasks( 'grunt-contrib-jshint' );

Running jshint first on all .js source files. Then running requirejs:build.

[jarrodpayne]

Hmm... It's not grunt-concurrent then. I was able to find out it was grunt-concurrent because the Fatal error: Unable to find local grunt. logged just before my concurrent task ran. In other words, several of my tasks would run, then once it got to concurrent it would log out the fatal error. Similar for you? Or, is it simply logging out fatal error immediately?