George Payne

Thanks @matchish, good find. The fix / bit of explanation is here: #310

@matchish #312 is the last PR before the `v4.0.0` release, so should be early next week.

@matchish `v4.0.0` has been released, including this fix. https://www.npmjs.com/package/@eventstore/db-client/v/4.0.0 https://github.com/EventStore/EventStore-Client-NodeJS/releases/tag/v4.0.0

The four options are: ### Separate method ``` ts await client.readStreamToArray('my-stream'); ``` ## Extension [1](#note1) ``` ts await client.readStream('my-stream').toArray(); ``` ### Helper ``` ts import { streamToArray } from '@eventstore/db-client';...

Proposal: Extend streaming read with `collect`: ```ts export interface StreamingRead extends Readable { // ... collect(): Promise; collect( reducer: (acc: T, event: E, i: number, self: this) => T, initialValue:...

Hi @yordis , Thanks for the input, we're still discussing this so any feedback is helpful / appreciated. > I would suggest trying to leverage `Array.from` since it is meant...

> Have you found any way to solve this locally? If you're using yarn 3+, you can apply the patch (#3306) directly to your the dependency: https://yarnpkg.com/features/protocols/#patch Run the patch...

> * Might be a breaking changes for the clients ? Yes, unless we also return a `created_ms` > * ?? Ticks should be milliseconds because it's a .netism or...

If anyone would like a temporary workaround, it's possible to add watch files via a custom output target. `watchAdditionalRegex.ts` ``` ts import { CompilerCtx, Config, OutputTargetCustom, } from '@stencil/core/internal'; import...

Hi @glenntws, Not sure if you're still interested in this as it's been over a year, but if possible could you try out the `2.2.0` release? It should be doing...