npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

compose-generator

v2.0.1

Published

Embed or sync generator functions with ease

Downloads

2

Readme

ComposeGenerator

Compose Generator designed to allow you easily synchronize or embed generator functions.

Usage

lets say you have generator functions genFunc1, genFunc2, genFunc3... If you want to synchronously use them, i.e. get generators and make synchronous .next() calls on them. you can use sync function.

const { sync } = require('compose-generator')

const compose = sync([ genFunc1, genFunc2, genFunc3 ])
const gen = compose([args1, args2, args3]) // args are arguments array of corresponding generator function.

for(const nextResults of gen) {
    // Use results of next calls...
}

Above nextResults is results array of .next() calls for each generator.e.g.

const nextResults = [
    { done: false, value: 1 } // gen1.next()
    { done: false, value: 'what?' } // gen2.next()
    { done: true, value: 'end' } // gen3.next()
]

Sync generator will continue until all composed generators are exhausted. And if some of them is returned earlier, then that final result will be returned for each .next() call until all they returned.

You can provide instead of array, a map of generator functions to Sync. Then nextResults will be map of results.

You can performe manual .next(arg) calls, or calculate super. for details see API.

If you want infinitly make synchronous calls, you can use Race composer, which will reset generator if it`s exhausted, like ticker.

If you want embed them like:

for(const v1 of gen1) {
    for(const v2 of gen2) {
        for(const v3 of gen3) {
            console.log({
                key3: v3,
                key2: v2,
                key1: v1,
            })
        }
    }
}

You can use Embed composer:

const { embed } = require('compose-generator')

// Up from down.
const compose = embed({
    key3: gen3,
    key2: gen2,
    key1: gen1,
})
const gen = compose({
    key3: args3,
    key2: args2,
    key1: args1,
}) // args are arguments map of corresponding generator functions.

for(const nextResults of gen) {
    // Use results of next calls...
}

In this case it will also reset generators until most outer generator is exhausted.

API

Composer

Eache of sync, race and embed functions we will call composer function.

Composer functions signature is( Not A Typescript ):

function composer(generatorFunctions: GeneratorFunction[]
 | { [key: string]: GeneratorFunction })
 : GeneratorFunction<callArgs[] | { [key: string]: callArgs }>

Composer function call result is a new generator function which is called compose. In cases when we considering generator, returned by compose generator function, we will also use word - compose, so be aware of the context.

Compose callArgs:

Call argument of compose generator function, must be corresponding function generators call arguments arrays array(or map, if generatorFunctions is map)

If undefined provided for some generator function callArgs, it will be called without arguments.

If undefined provided for the whole argument callArgs, generator functions will be instantiating without arguments.

Call examples:

  • with generator functions array:

    const compose = composer([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
  • with generator functions map:

    // Or with Map
    const compose = composer({ 
        key1: genFunc1,
        key2: genFunc2,
        key3: genFunc3
    })
    const gen = compose({
        key1: [ arg0, arg1 ],
        key2: undefined, // same, as if not provided or empty array provided.
    })
    // If no callArgs
        compose()
        // same as ->
        genFunc1()
        genFunc2()
        genFunc3()

After generator functions composed with some of the provided composer functions, each result of .next(arg) call on the compose generator will be an array( or map, depending on what provided to composer) of next call results for each generator included in composition, e.g.

const nextResults = [
    { done: false, value: 1 } // gen1.next(arg1)
    { done: false, value: 'what?' } // gen2.next(arg2)
    { done: true, value: 'end' } // gen3.next(arg3)
]

Sync

Sync extends Composer

Compose .next(nextArg):

.next(nextArg) call argument must be function, undefined, or an array(or map if generatorFunctions is map) of .next(arg) call arguments for appropriate function generators,

If nextArg is function, it`s signature is( Not A Typescript ):

(lastResults: IteratorResult<any, any>[]
| { [key: string]?: IteratorResult<any, any> },
key: string) => any
  • lastResults is an array(or map) of results of compositions last generators .next(arg) calls.
  • key is a key of current generator
  • return is a value to call currentGenerator.next() with.

This function will be called for each generator from start, and its returned value will be used as .next() call argument for appropriate generator.

Next Call examples:

  • with array or map:
    const compose = sync([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
    
    gen.next([nextArg1, nextArg2])
    // same as
    gen1.next(nextArg1)
    gen2.next(nextArg2)
    gen3.next()
  • with undefined
    const compose = sync([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
    
    gen.next()
    // same as
    gen1.next()
    gen2.next()
    gen3.next()
  • with function
    const compose = sync([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
    
    let lastKey
    gen.next((lastResults, key) => {
        const lastKeyTmp = lastKey
        lastKey = key
        if(!lastKeyTmp) return // same as gen1.next()
    
        return lastResults[lastKeyTmp].value // same as super of next values
    })
    // same as super.
    const g1 = gen1.next()
    const g2 = gen2.next(g1.value)
    const g3 = gen3.next(g2.value)

If some of the generators exhausted, it's last value will be used until all generators exhausted. i.e. if some of them finished with value { done: true, value: 'finish' }, it will be returned for subsequent compose next calls.

Race

Race extends Composer

The main difference of Race from Sync, is that it will reset generators each time they exhausted, so return values will not be included in results. Reset will be performed with same callArgs provided to Composer.

Embed

Embed extends Composer

Compose .next(nextArg):

.next(nextArg) call argument must be function, or any other value.

If nextArg is function, it`s signature is same as for Race and Sync, But with arguments different description ( Not A Typescript ):

(lastResults: IteratorResult<any, any>[]
| { [key: string]?: IteratorResult<any, any> },
key: string) => any
  • lastResults is an array(or map) of results of compositions last generators .next(arg) calls.
  • key is a key of current generator
  • return is a value to call currentGenerator.next() with.

This function will be called each time starting from first generator, and continue until some of them is not exhausted, if they are all exhausted, compose generator will be returned.

Each time it is called, its returned value will be used as .next() call argument for appropriate generator(for which it is called). If after .next() generator is exhausted, i.e. done=true, this function will be called for next generator with lastResults containing appropriate return values for last generators.

If some of the generators exhausted, it will be reseted with initial callArgs.

Next Call examples:

  • with NotFunction:
    const compose = embed([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
    
    gen.next(nextArg)
    // same as
    const gen1Val = gen1.next(nextArg)
    if(gen1Val.done) {
        gen2.next(nextArg)
        // ... and so on
    } else {
        // next will be not called
    }
    // Finial merged state will be here.
  • with function
    const compose = sync([ genFunc1, genFunc2, genFunc3 ])
    const gen = compose([ [ arg0, arg1 ], [ ] ])
    
    let lastKey
    gen.next((lastResults, key) => {
        // This function will be called for first generator every time
        // and subsequent calles will be performed, when it is returned after calling .next()
    })