You are not required to create packages to use Fly! You can simply pass your transformer function to `Fly.prototype.filter` and be done with it. I think plugins should be true thin wrappers to whatever utilities you are trying to incorporate into your build task.
Compare this to gulp where you sometimes need to use vinyl and other abstractions, plus stream wrappers and other deps.
Thanks for the update bucaran! If that's the case, I'm definitely going to dive deep in it; that's exactly what I've been hoping for in a next-gen build-tool (WebPack just doesn't do it for me)!
I am sorry I missed this post.
You are not required to create packages to use Fly! You can simply pass your transformer function to `Fly.prototype.filter` and be done with it. I think plugins should be true thin wrappers to whatever utilities you are trying to incorporate into your build task.
Compare this to gulp where you sometimes need to use vinyl and other abstractions, plus stream wrappers and other deps.