Expose untranspiled CJS & ESM modules #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @kevinbarabash, every 3 months or so I'll get really disappointed at the total lack of consistency in JS iteration standards. A couple of days ago I really started getting into generators, and this just threw into relief how much worse this has become in ES6. Why can't I interpolate keys during lazy iteration? God knows.
Anyway, functify is perfect to paper over these shortcomings – but the README is misleading and I think in this day and age it's reasonable to offer the source untranspiled for transformation at the consumer's discretion – all of this works in my browser at present.
This patch tidies things up a bit. Thanks for the great work in providing a consistent, functional, itterable interface!