Watch config file

[RyanZim]

Currently when the -w & -c options are specified, postcss rebuilds the css files only when the input file changes (and does not reload the config file). If you change the config file, you need to cancel the process and re-run it.

This is irritating for me since I call postcss from an npm script that starts a dev server, my browser, etc. This script takes a bit of time to start or cancel, so I waste a lot of time when changing the config file. ⌛

I think that when both the the -w & -c options are specified, postcss should reload the config and rebuild the css when a change is detected in the config file.

I'm not sure if I can submit a PR or not. (I'm extra busy right now)

[RyanZim]

@pirxpilot, @watilde bump.

I'm currently wrapping postcss with chokidar-cli as a workaround.

[RyanZim]

@pirxpilot @watilde @ai bump, bump, bump.

[watilde]

Oops so sorry for my late response. Let me check it.

[watilde]

Thanks for the feature request. I agreed with this! I will try to create a patch and also let me keep the thing it's still patch-welcome as well.

[RyanZim]

@watilde Currently there's no good way to do this with yargs. Let's put this on hold until yargs/yargs#585 is resolved.

[RyanZim]

We will be supporting the common config in v3, which should allow us to do this, so adding this issue to the v3 milestone.

[michael-ciniawsky]

@RyanZim Seems to be trickier then I thought 😛 , do you have started anything in this regard already?

[RyanZim]

@michael-ciniawsky I'll hit this asap.

[michael-ciniawsky]

@RyanZim I played around with declaring a variable in global scope assigning the config.file configFile = arr[1].file to, but adding it to watcher.watch([ input, configFile ]) doesn't work because of watcher logic. The question is how to trigger a rebuild of all files, but tbh I didn't check chokidar docs for all possible optons until now.

[RyanZim]

Don't worry, I'll get it.

[michael-ciniawsky]

@RyanZim fixed via #69