Avoid multiple restart with big grunt processes

[Pierre-Antoine Delnatte]

Hi,

I have a little problem with nodemon : when my watch process is launched, triggering nodemon, nodemon restart on each change, as showed in this capture :

(I have blured the name of the project which is under NDA from my client, sorry)

What can i do to avoid that ?

Thanks in advance,

[Chris Wren]

I am getting a 404 on the link can you re upload?—
Sent from Mailbox for iPhone

On Wed, Feb 26, 2014 at 4:37 PM, Pierre-Antoine Delnatte
[e-mail] wrote:

Hi,
I have a little problem with nodemon : when my watch process is launched, triggering nodemon, nodemon restart on each change, as showed in this capture :

(I have blured the name of the project which is under NDA from my client, sorry)
What can i do to avoid that ?

Thanks in advance,

Reply to this email directly or view it on GitHub:
#37

[Pierre-Antoine Delnatte]

Can you see it now ?

[Chris Wren]

By default nodemon will watch every .js file, so it seems to be triggering a restart based on a change unrelated to your server. Could you post your config for the nodemon task?

[Chris Wren]

Also, you can check out the ignore and watch options to make sure it only restarts when server files are changed.

[Pierre-Antoine Delnatte]

Here it is :

   nodemon:
        work:
            script: "bin/project.js"
            options:
                ext: "js,jade"
                watch: [ "bin" ]
                ignore: [
                    "files/**"
                    "node_modules/**"
                    "src/**"
                    "static/**"
                ]

[Chris Wren]

Are you running grunt-nodemon version 0.2.0?

If so, you could you run your grunt task with the -v or --debug flags which will show you more output so that you can see what file is triggering the nodemon restart.

[Pierre-Antoine Delnatte]

Okay, i'll do that.

I close the issue until I see if the problem is caused by me or resulting from a bug in grunt-nodemon.

Thanks for your help. 👍