Issues
- 4
Uncaught Error: define cannot be used indirect
#54 opened by vvetsko - 3
ES6 Module transpiler
#53 opened by gordonbrander - 0
Consider making passback part of reducers itself.
#52 opened by Raynos - 0
Document hub vs cache
#51 opened by Raynos - 0
Benchmarks
#49 opened by Raynos - 1
method and npm dedup is too unreliable
#47 opened by Raynos - 31
wrap the result of all things in hub
#45 opened by Raynos - 6
Step through debugging
#46 opened by Raynos - 2
`reductions(acc, value)` vs `fold(value, acc)`
#43 opened by Raynos - 14
Run tests on ci.testling.com
#27 opened by Raynos - 5
error handling
#32 opened by Raynos - 7
Do not capture exceptions
#26 opened by Raynos - 1
Remove dependency on eventuals
#28 opened by Gozala - 1
Make reducers compatible with add-on sdk
#29 opened by Gozala - 6
Multiple folds + reduced
#33 opened by Raynos - 1
retape + testling
#38 opened by Raynos - 3
Handling errors after end and reduced
#34 opened by Raynos - 1
- 3
Be opinionated. Recommend a backpressure protocol.
#37 opened by Raynos - 3
Implement `finalize` function
#35 opened by Gozala - 5
- 1
write about how reducers compose transformations
#11 opened by Gozala - 4
- 5
Signal, Channel, emit do not belong in reducers
#22 opened by Gozala - 20
channels are harmful
#23 opened by Gozala - 0
- 0
write tests and documentation for cache function
#18 opened by Gozala - 0
document reducers backchannel
#12 opened by Gozala - 5
- 0
write how meta-items are used for error handling
#13 opened by Gozala - 0
Simplify error hanling code
#16 opened by Gozala - 0
Simplify end of stream meta item
#17 opened by Gozala - 0
- 3
- 3
No main field, no index.js
#9 opened by Raynos - 1
implement zip
#10 opened by Gozala - 0
Implement sugar for dom APIs
#1 opened by Gozala - 1
Write todo app example
#2 opened by Gozala - 0
add chaining support
#3 opened by Gozala - 1
More docstrings, literate commenting
#4 opened by gordonbrander