Emitted code uses regeneratorRuntime #7
Comments
|
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. |
|
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. |
|
No stress from my side, I wrote an alternative implementation that doesn't use It seems like you are only using 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 |
|
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. |
|
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 |
- Breaking Change: Dropping support for Node 11 and below. - Breaking Change: Dropping support for Flow. - Bug Fix: Resolves #5. Event handlers are cleaned up after each iteration, fixing some memory leak issues. - Bug Fix: Resolves #7. Code no longer depends on babel runtimes or regenerator. - Bug Fix: Handles stream not buffering due to starving the event loop. - Feature: Resolves #1. Now handles `.throw` and `.return` hooks on the async iterator. - Feature: Properly closes stream when finished. - Feature: Added support for TypeScript. - Feature: Support for Node.js versions 12, 14, and 16. - Chore: General overhaul of project setup (should not impact what is published).
|
Release in v1.0.0 |
The emitted code that this module publishes, uses
regeneratorRuntimewhich makes it fail without that. Because of this, you cannot use this module out of the box on e.g. Node.js 10.x.The text was updated successfully, but these errors were encountered: