Browserify usage about taskr HOT 7 CLOSED

Good question. I will have an answer as soon as I release 0.2.0

Definitely no wrappers or painful abstractions.

No problem with using require, but I haven't tested using import in a Flyfile. I like this.

from taskr.

@girvo Alright, so [email protected] is out.

Now we have support for async tasks in plugins.

For example a plugin for browserify could look like this:

function myFilter (data, options, cb) {
  // do browserify stuff here
}

this.filter("myPlugin", (source, options) => {
  return this.defer(myFilter).call(this, source, options)
})

I haven't actually done this as I just bumped this version and I still have some TODOs before I can tackle a browserify plugin.

But with async support this should be possible regardless of how browserify works.

Now, Fly does not use streams so different from gulp in which a browserify plugin would be discouraged, it would be ok in Fly, since it would just be a couple of LOC and we want to integrate nicely into Fly promise sequence.

from taskr.

@girvo Now we have a work around. It's not perfect as it ends up reading IO twice due to Fly's inability to handle streams at the moment, but this should change when channels land in Fly somewhere around 0.4.0 or 0.5.0

from taskr.

@MadcapJake Comments?

from taskr.

With the latest fly-browserify, we now have a working implementation. I for one, am happy with where it's at even with the extra IO because at least it works! 😅

Also, with regards to imports, I am currently using earlify with it and it works just fine! You can set all the options that browserify normally accepts too.

As an example, right now I'm working on a gh-pages website written entirely in Earl Grey and I'm using fly to build it. It's really basic right now but it works and I can jump in and uncomment uglify when I'm ready for production (Which is kind of a neat way to think about it as I can jump in to my Flyfile and treat each filter as switches to be turned on and off). Check it out here.

Many thanks to @bucaran for finalizing a proper browserify solution too! 👍

from taskr.

This issue could be closed. @girvo has contacted me on fly-browserify's repo, we were stuck at a bug but I've written a fix and I'm just waiting to hear back on whether that has fixed it.

from taskr.

@MadcapJake Thanks!

from taskr.