Emitted code uses regeneratorRuntime

[LinusU]

The emitted code that this module publishes, uses regeneratorRuntime which makes it fail without that. Because of this, you cannot use this module out of the box on e.g. Node.js 10.x.

node_modules/stream-to-async-iterator/stream-to-async-iterator.js:134
            var _ref = _asyncToGenerator(regeneratorRuntime.mark(function _callee() {
                                         ^

ReferenceError: regeneratorRuntime is not defined
    at node_modules/stream-to-async-iterator/stream-to-async-iterator.js:134:42
    at node_modules/stream-to-async-iterator/stream-to-async-iterator.js:197:10
    at Object.<anonymous> (node_modules/stream-to-async-iterator/stream-to-async-iterator.js:246:2)
    at Module._compile (internal/modules/cjs/loader.js:702:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)
    at Module.require (internal/modules/cjs/loader.js:650:17)
    at require (internal/modules/cjs/helpers.js:20:18)

[basicdays]

Good point, will need to see if there's a way to publish this both transpiled and non-transpiled. You happen to know if there's any standard approach to that? Otherwise I could just publish it twice.

[basicdays]

Tell you what, in the meantime I'll just switch this out to use babel-runtime as a dependency. I'll have to consider a way to publish this without transpilation so it "just works" in newer node versions.

[LinusU]

No stress from my side, I wrote an alternative implementation that doesn't use await in the source code at all: https://github.com/LinusU/async-chunks/blob/master/index.ts

It seems like you are only using await at one place, it would probably be easy to get rid of 🤔

On the other hand, another way to solve it would probably be to get flow to target es2015 instead of es5. At least that is how it works in TypeScript, was a while since I last used flow.

Basically, that will tell flow that the target supports generators (which all current versions of Node.js does) and thus won't need regenerator to work. This is probably the best solution since the output code will probably be more performant.

[basicdays]

Yeah I'm bumping the version to node 6 and dropping node 4 support. I also intend to switch out flow to typescript as well soon, since that's what I use these days.

[basicdays]

Just released a version that should remove the global dependency on regenerator runtime. I didn't release it out of beta yet however, so if you would like to try it out, it's released under stream-to-async-iterator@beta.

[basicdays]

Release in v1.0.0