grunt throw "Recursive process.nextTick detected"

Question

I'm running Lion 10.9.2 with nodejs v0.10.26

I want to setup an automated compilation on sass files and a live reload with grunt, nothing complicated but...

When running grunt watch I get the following error

(node) warning: Recursive process.nextTick detected. This will break in the next version of node. Please use setImmediate for recursive deferral.

util.js:35
  var str = String(f).replace(formatRegExp, function(x) {
                      ^
RangeError: Maximum call stack size exceeded

here is the Gruntfile.js

module.exports = function(grunt) {

    // Project configuration.
    grunt.initConfig({
        pkg: grunt.file.readJSON('package.json'),

        sass: {
            dist: {
                files: {
                    'assets/css/styles.css': 'assets/sass/styles.scss'
                }
            }
        },
        watch: {
            all: {
                files: 'index.html', // Change this if you are not watching index.html
                options: {
                    livereload: true  // Set livereload to trigger a reload upon change
                }
            },
            css: {
                files:  [ 'assets/sass/**/*.scss' ],
                tasks:  [ 'sass' ],
                options: {
                    spawn: false
                }
            },
            options: {
                livereload: true // Set livereload to trigger a reload upon change
            }
        }

    });

    grunt.loadNpmTasks('grunt-contrib-watch');
    grunt.loadNpmTasks('grunt-contrib-sass');

    grunt.registerTask('watch', [ 'watch']);

    grunt.registerTask('default', [ 'sass', 'watch' ]);

};

and here is the package.json

{
  "name": "application",
  "version": "0.0.1",
  "private": true,
  "devDependencies": {
    "grunt": "~0.4.2",
    "grunt-contrib-watch": "~0.5.3",
    "grunt-contrib-sass": "~0.7.3"
  }
}

score 299 · Accepted Answer · answered Mar 14 '14 at 15:31

299

I finally figured out a similar problem I was having with SASS. I was using

grunt.registerTask('sass', [ 'sass']);

The trick was that Grunt doesn't seem to like the repetition in names. When I switch to

grunt.registerTask('styles', [ 'sass']);

Everything worked as it should.

answered Mar 14 '14 at 15:31

Bob Rockefeller

4,492
2
28
35

2

awesome, thanks for spotting this. I realised we don't need to register a single task anyway, because grunt will run 'grunt sass' when you type that into the command line. – stefan Apr 01 '14 at 06:23
1

Thank you for answering this... I've been bashing my head on the desk for the last hour and a half figuring out why the `grunt-bower-concat` plugin was giving me that output. – Derek Jul 09 '14 at 02:54
Oddly worked for me fine with sass, but broke on watch, thanks – Ryan Knell Mar 02 '15 at 03:55

score 17 · Answer 2 · answered Mar 10 '14 at 22:45

17

Just had this problem. Resolved it by removing grunt.registerTask('watch', [ 'watch']);

answered Mar 10 '14 at 22:45

Abraham Parangi

171
3

score 11 · Answer 3 · answered Apr 20 '14 at 14:54

11

I just fixed a similar error "Recursive process.nextTick detected" causing by command: grunt server

The solution? Use sudo grunt serve instead

answered Apr 20 '14 at 14:54

krazyweb

141
3

this should never be the solution. `sudo` shouldn't be used unless its something that is actually changing your system. It sounds like you did `sudo npm install` which is often bad – Eddie Monge Jr Jan 13 '15 at 19:34

score 1 · Answer 4 · edited May 23 '17 at 12:17

1

you could try this one, it fixed the issue for me, working with Yeoman 1.3.3 and Ubuntu 14.04 Grunt watch error - Waiting...Fatal error: watch ENOSPC

edited May 23 '17 at 12:17

Community

1
1

answered Nov 14 '14 at 20:13

hybrisCole

74
5

score 1 · Answer 5 · edited May 23 '17 at 10:31

1

I was getting error in even trying to install grunt. Running npm dedupe solved my problem as answered here: Grunt watch error - Waiting...Fatal error: watch ENOSPC

edited May 23 '17 at 10:31

Community

1
1

answered Jun 18 '16 at 21:17

dreamerkumar

1,540
1
18
28

score 0 · Answer 6 · answered Dec 10 '14 at 21:01

Alternative solution: check your watch for an empty file argument.

Here's an excerpt of my gruntfile

watch: {
  all: {
    options:{
      livereload: true
    },
    files: ['src/scss/*.scss', 'src/foo.html',, 'src/bar.html'],
    tasks: ['default']
  }
}

In my case, I could recreate the original poster's error on demand with the empty argument above.

grunt throw "Recursive process.nextTick detected"

6 Answers6

Linked