Remove grunt dependencies from builder/patternlab.js

[bmuenzenmeyer]

Converting the builder to straight-up node will decouple the core components from the build tool.

• Helps with unit testing and single responsibility
• More easily allows patternlab-node to be reused, in, say, something like gulp

[ivanmayes]

Agreed. We should separate a grunt or gulp version into different repos that extend the base plab-node repo.

[addyosmani]

+9001. It's significantly easier to understand what the core components do when you're not trying to mentally decouple them from the Grunt setup.

[bmuenzenmeyer]

Glad to hear support for this. I will think on how best to accomplish a core | grunt | gulp approach without sacrificing ease of use to existing or new users. I suspect that some amount of bumpiness will occur either way, as @dmolsen has wrestled with as pl-php matures.

As @addyosmani has on his website,

First do it, then do it right, then do it better

I will likely write the pure node implementation synchronously to start, unless anyone can help me architect a more async model from the get-go. :)

[VinSpee]

I'd just like to chime and and say I'm really really excited about this. Thanks for all of the hard work, and I'm looking forward to it!

[bmuenzenmeyer]

FYI: this is now in dev. Most of my node is still synchronous. Will be working on that, and gulp support. @addyosmani I was reading the gulp plugin guidelines and my interpretation was that patternlab may be too specific and too broad for gulp. Perhaps further refactoring of the node module in dev will reveal a clearer path for me.

I would appreciate your thoughts on the matter.

[bmuenzenmeyer]

To all that care, this is now in master. Next steps, async, refactor, gulp!?