i don't get it. co already allows yielding promises.
Am Samstag, 30. August 2014 14:09:46 UTC-7 schrieb Dean Landolt:
>
> I was trying to find a clean way to adapt co to be able to be able to
> yield promise or non-promise values (e.g. use yield like the `when` method
> of a lot of promise libs
read it carefully. he says he won't be using node anymore except for web
stuff. he just doesn't do web sites right now, so node doesn't suite him
anymore.
but most of his stuff will still be maintained anyways so don't worry about
it
On Friday, July 4, 2014 8:40:25 AM UTC-7, vitor.sh...@gmail.
had the same issue recently: https://github.com/joyent/node/issues/7767
On Tuesday, June 10, 2014 9:50:54 AM UTC-7, greim wrote:
>
> I'm using node 0.11.13 with --harmony running koa and compressing using
> koa-compress, which in turn uses zlib. Here's the error right before the
> process dies:
no, that will break everything. plus, what happens if there's "await" in
ES7? they would have to change everything again.
On Saturday, December 21, 2013 10:57:14 AM UTC-8, q2dg2b wrote:
>
> I think the question most important about this topic it is:* will Node.js
> substitute callback by generat
ly, you'll have to do do `writer.end()` after
all the readers emit an `end` event. in other words, you would have to do
control flow.
On Saturday, October 26, 2013 3:43:33 PM UTC-7, Jonathan Ong wrote:
>
> the read stream #1 will end the write stream when it is done. you don
the read stream #1 will end the write stream when it is done. you don't
want want that to happen. you'll want to `writingStuff.end()` yourself (not
specifically this case, but in general, since the read stream #1 could take
longer than #2):
reader1.pipe(writer, {end: false})
process.nextTick(f
i wouldn't suggest https://github.com/rsms/node-imagemagick. it is no
longer maintained.
use https://github.com/aheckmann/gm instead since it is at least maintained
(by me now as aaron is busy with mongoose). even better, just use
require('child_process').execFile.
On Sunday, August 11, 2013 5
I'm trying to create a wrapper around child_process.spawn but I'm having
trouble understanding streams2. i know how to do this with the "old" streams
suppose I have a function BlackBox with the external api that looks like
this: (|s are pipes)
inputStream | BlackBox | outputStream
but as Blac
just don't bother publishing it. use github namespaces in npm.
{
"dependencies": {
"merge": "stagas/merge"
}
}
On Saturday, May 25, 2013 1:34:51 AM UTC-7, Alex Kocharin wrote:
>
>
> RPG name generator could do the job. :)
>
> --
> // alex
>
> 25.05.2013, 10:49, "George Stagas" >:
> >
