Does spawn:false have a known issue on Windows + livereload?

[Francisc]

Hello,

Watch + livereaload works great. However, if I set spawn:false although the changes are caught, livereload doesn't fire.

Is this a known thing? I'm tempted by the faster response of the watcher when spawnning is false.

[shama]

Could you post your Gruntfile and node.js version? Thanks!

[Francisc]

Hello.

I'm using Node v0.10.26 on Windows 7x64.

Here's the watch config:

watch:{
    options:{
        spawn:false,
        debounceDelay:50
    },
    sass:{
        files:'css/**/*.scss',
        tasks:['sass:watcher']
    },
    livereload:{
        options:{
            livereload:35729
        },
        files:'css/style.css'
    }
}

[Francisc]

Forgot to mention that if I remove spawn:false, livereload works.

When set to false, livereload doesn't update the browser CSS but the watcher does observe file changes and runs the sass:watcher task.

[Richard-Walton]

I am experiencing the exact same issue.

[Yankovsky]

same

[Yankovsky]

It works each second time

[Yankovsky]

I kind of fixed this issue by adding options: { livereload: true } to each watch task

[ejoo]

Same issue. I still lacking understanding about what the spawn means here.

[dev-bjoern]

having the same problem. grunt-cli v1.2.0 grunt v1.0.1