watch support

[serapath]

atomify-js has a "watch" option, but atomify-css doesnt have, thus, atomify in "watch mode" will recompile javascript when a change occurs, but a css change will not make the css be rebuild.

[joeybaker]

@serapath you're right. We don't have a native watch option in atomify-css, but we do have a way to do this if you use atomify. Would that do it for you?

[serapath]

how does it work? :-)

[joeybaker]

https://github.com/atomify/atomify#optsserver has some docs. Basically, atomify will spin up a webserver and watch all your files for you. It gets you live-reload as well.

[serapath]

the main css file i use in projects contains nothing but 1+ "@import" statements.
it does not help me to watch them, because most of the live changes happen in the imported files or the files they import (which needs a "watch statement" for all of the npm-ish @imported css files).
...
maybe i dont get it, but it would be helpful if there was an example of hot to get the "optsserver" settings right so that it works...

[joeybaker]

Yup! Having one main css file is totally fine – that's what I do too. https://github.com/Techwraith/ribcage-preview/blob/master/index.js might give you an idea of how to setup the live reload server.

[serapath]

Hey hey, in order to solve this issue, i filed 3 pull requests with atomify, atomify-css and rework-assets which reference THIS issue in their commit message.
Could you take a look and if they are all acceptable - it would be great to solve this issue here by actually accepting those :-)

[joeybaker]

@serapath can you just link all the PRs that need to be merged for this? I want to be sure they land together.

[serapath]

They are all listed on GITTER. It's 3 PRs, where on is in rework-assets

[joeybaker]

ok - fixed it and updated all pull requests atomify/atomify#46 and #26
I wrote a small tutorial into the atomify/readme.md which you could review
I also informed @conradzim about conradz/rework-assets#11 which is necessary in order to make the change work.