bmuenzenmeyer
commented
8 years ago At one time, I packaged up "standard" grunt and gulp tasks within core and then a user could directly consume them, but this was still inadequate. My understanding is that someone can actually require a gruntfile or gulpfile directly (http://macr.ae/article/splitting-gulpfile-multiple-files.html at least for gulp) making these still consumeable.
This would avoid the mess that occurs if one wanted to run patternlab node as a npm dependency.
That documentation is 1.X only and I doubt it applies to the 2.X code anymore. With 2.0, we fully intended Pattern Lab to act as an ecosystem and have focused on standalone first (it's hard enough making everything work, let alone make PL consumable in every which way people request). We expect people to write their own editions - and therefore the tasks that ship with this repo and it's gulp sister are samples (albeit samples most people would find mandatory).
That said, if you can find patterns that match the spirit of my above comment but make for more consumable code, please submit a PR!
hjylewis
Is there a reason this isn't set up as a grunt plugin for easy installation and configuration using
grunt.loadNpmTasks('edition-node-grunt')andgrunt.initConfiginstead of the config.json file?This would avoid the mess that occurs if one wanted to run patternlab node as a npm dependency.