Bacon.js 2.0
See original GitHub issueI’m trying to come up with a version 2.0 in the near future, with at least the following changes:
#700 Remove lazy evaluation of event values
#706 Make Bacon.once and friends asynchronous
#708 Use rollup to build everything from ES6 modules
#711 Force asyncness of all streams created with any of the stream constructors
EDIT: all four PRs merged into the 2.0 branch.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
API reference - Bacon.js 2.0
Bacon.js is a functional reactive programming library for javascript.
Read more >baconjs - npm
A small functional reactive programming lib for JavaScript. Turns your event spaghetti into clean and declarative feng shui bacon, by switching from imperative ......
Read more >BACON.JS 2.0.2 CDN links - CDNPKG .com
BACON.JS 2.0.2 CDNs. Description, A small functional reactive programming lib for JavaScript. Website, http://baconjs.blogspot.com. Sources URL, https ...
Read more >Bacon.js - Functional Reactive Programming library for ...
Bacon.js is a functional reactive programming library for javascript. ... EventStreams and constant values using the given n-ary function f(v1, v2 ...) ....
Read more >bacon-love - npm Package Health Analysis - Snyk
bacon-love. v2.0.0. A Nodeschool type workshop for Functional Reactive Programming and Bacon.js For more information about how to use this ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

My colleages suggested this:
EventStreams emit asynchronously regardless of how they were created.This would apply to streams created using
fromESObservable,fromCallbackand friends.This would require a mechanism in
fromBinderor theEventStreamconstructor to ensure that events are not emitted synchronously as a respose to subscription.Properties are still allowed to emit their current value syncrhonously as there’s no downside to that.
Pls vote up/down for this. I’m cautiously supportive myself
EDIT: #711 merged
Closing the Issue. Will handle in Pull Request #709