Run commands and tasks in parallel to speed up your build. about generator-veams HOT 5 CLOSED

You could switch to grunt-concurrent, which is imho much easier to use and it makes bgShell and grunt-parallel obsolete.

from generator-veams.

that is not the same. to speed up the workflow I decide to run native comands for compass. that is much faster than grunt-contrib-compass. to optimize the tasks in general we need grunt-concurrent or grunt-parallel. so both options are great ...

from generator-veams.

OK, I didn't know that using bgShell is faster. Did you test that by yourself or where does this information came from? I'm asking because grunt-contrib-compass uses ruby and the rubygem compass like it can be used in bgShell.

Pro using compass with bgShell:

• there is no possible version conflict with installed version of compass, because it uses command line compass and does not add extra stuff

Contra:

• the configuration of bgShell is more complicated and the current release of generator-prototype hides the error messages from ruby away from the user (try install generator prototype without ruby, rubygems and compass - it does not tell anything to the user - maybe stdout and stderr defaults are set to false)

from generator-veams.

bgShell is much faster. in current projects i reduced the amount from 7-9 seconds to 1-2 seconds. the problem is, that the watch task have to start compass via grunt-contrib-compass every time you change a scss-file and in my solution it works in background as independent watch task.

pro:
furthermore it adds the possibility for sourcemaps and does not throw an error like in the newer versions of grunt-corntrib-compass ...

contra:
it is a bit more difficult, but not that hard.
did not know it with the error messages. will looking for a solution.

from generator-veams.

grunt-concurrent is integrated in 0.4.9

from generator-veams.