The v11 change is causing me to rethink separately instantiating changesReader instances myself, so that I can have one per follow of a particular changes stream.
Putting this issue here as a possible point to contribute an alternative behavior for changesReader or factory of changesReader instances.
Would be great to be able to remove my now-outdated fork of changesReader by itself, outside nano proper!
The
v11change is causing me to rethink separately instantiatingchangesReaderinstances myself, so that I can have one perfollowof a particular changes stream.Putting this issue here as a possible point to contribute an alternative behavior for
changesReaderor factory ofchangesReaderinstances.Would be great to be able to remove my now-outdated fork of
changesReaderby itself, outsidenanoproper!