nordfjord
commented
6 years ago you could always do something like
const attempt = fn => (...args)=> {
try {
return fn(...args);
} catch(e) {
console.error(e);
}
}
const safe_combine = (fn, streams)=> flyd.combine(attempt(fn), streams);To solve this on your side.
The reason errors break applications is because flyd has a global inStream variable that is populated with the current stream being updated. When an error happens inStream is never reset to undefined and flyd assumes everything is happening in a stream body and pushes results and updates to the toUpdate array.
c-dante
StreetStrider
It is possible to create dead streams if you have code that runs in async frames such as setTimeout or in event listeners.
This gist has the example, you can run it in RequireBin and see int the console.
I'm using a setTimeout to push to a stream where a child stream throws an uncaught exception. The only place to catch the exception is inside the stream. The result is that the parent stream is now broken / unusable. You can update values to any stream, but no updates occur and no new streams can be attached.
I don't THINK that this warrants a change to the base level combine API, but perhaps a safer api that wraps stream updates in error handling can be useful. If you run into this case, you end up with a seemingly unresponsive app with no other errors than the one that breaks the stream.
There also seems to be no way to recover or investigate this state once you're in it.