You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In response to issue #21, I've decided to create this thread to track changes between released version of the npm package.
Make sure you subscribe to this issue if you want to be notified of changes in the API.
client.createConnection If calling with a TcpEndpoint ({hostname, port}) as second parameter, you need to change the hostname property to host. Also it is now recommended to use a string as second parameter, you can replace TcpEndpoint with "tcp://hostname:port".
New features
Implement cluster discovery using dns #19 You can now connect to a cluster using dns discovery. Just pass "discover://my.dns:2113" as second parameter to client.createConnection. Replace 2113 with the http port.
New project name/package name: node-eventstore-client
Sorry for the annoyance but the project name was bugging me for a while. Also I will probably start a go version of the port soon. This naming scheme is more clear.
Implement ssl connection #3 Ssl connection is now implemented see test/connection_test.js for example and read eventstore docs on how to set it up. Note: testing was only done with a self-signed certificate and validateServer: false, if you experience issue with CA signed certificate let me know.
Also here's some important notes about the subscriptionDropped / reconnect behavior.
Only catchUp subscriptions (subscribeToAllFrom or subscribeToStreamFrom) will automatically resubscribe and continue from where they left off after a client reconnect.
There is no need to manually handle re-subscription for these type of subscriptions.
CAVEAT: catchUpSubscriptions will only continue after reconnect if they reached their "live processing" phase, i.e. the liveProcessingStarted event was fired. If the subscription dropped during the catchUp phase the subscription will NOT continue automatically after a reconnect.
strange reconnect error #60 Fixed an issue with the tcp connection logic where it did not close the connection when the socket was closed due to a transmission error.
#85 Fixed an issue where AppendToStream with expected version any and existing event did result in the event being saved. It was due to a protobufjs issue. Was fixed after updating it to latest version.
Activity
nicdex commentedon Feb 6, 2017
0.0.25 CHANGELOG
Breaking Changes
New features
nicdex commentedon Feb 6, 2017
0.0.26 CHANGELOG
Breaking Changes
None
Bugs
Position#20 Fixed an issue with missing Position in TypeScript definition file.nicdex commentedon Feb 18, 2017
0.0.27 CHANGELOG
Breaking changes
None
Improvements
nicdex commentedon Feb 25, 2017
0.0.28 CHANGELOG
Breaking changes
None
Bugs
nicdex commentedon Mar 8, 2017
0.0.29 CHANGELOG
Bugs
nicdex commentedon Mar 25, 2017
0.0.30 CHANGELOG
Bugs
nicdex commentedon Apr 1, 2017
0.0.31 CHANGELOG
Improvements
#30 Set return type for PersistentSubscriptionSettings.create() so it doesn't break tslint validations.
nicdex commentedon Apr 16, 2017
0.0.32 CHANGELOG
Improvements
nicdex commentedon Apr 16, 2017
0.1.0 CHANGELOG
No changes from last release
nicdex commentedon May 15, 2017
0.1.2 CHANGELOG
Breaking changes
None
New feature
nicdex commentedon May 17, 2017
0.1.2 CHANGELOG - project rename
No changes
New project name/package name: node-eventstore-client
Sorry for the annoyance but the project name was bugging me for a while. Also I will probably start a go version of the port soon. This naming scheme is more clear.
nicdex commentedon Jun 5, 2017
0.1.3 CHANGELOG
Breaking changes
None
Bugs
nicdex commentedon Jun 24, 2017
0.1.4 CHANGELOG
Bugs
nicdex commentedon Jul 1, 2017
0.1.5 CHANGELOG
Breaking changes
Improvements
7 remaining items
nicdex commentedon Feb 19, 2018
0.2.2 CHANGELOG
Enhancement
nicdex commentedon Mar 11, 2018
0.2.3 CHANGELOG
New feature
nicdex commentedon Sep 1, 2018
0.2.4 CHANGELOG
Improvements
nicdex commentedon Oct 21, 2018
0.2.5 CHANGELOG
0.1.12 CHANGELOG
Bugs
Also here's some important notes about the subscriptionDropped / reconnect behavior.
Only catchUp subscriptions (subscribeToAllFrom or subscribeToStreamFrom) will automatically resubscribe and continue from where they left off after a client reconnect.
There is no need to manually handle re-subscription for these type of subscriptions.
CAVEAT: catchUpSubscriptions will only continue after reconnect if they reached their "live processing" phase, i.e. the liveProcessingStarted event was fired. If the subscription dropped during the catchUp phase the subscription will NOT continue automatically after a reconnect.
nicdex commentedon Dec 5, 2018
0.2.7 CHANGELOG
Bugs
nicdex commentedon Jan 17, 2019
0.2.8 CHANGELOG
Bugs
nicdex commentedon Feb 18, 2019
0.2.9 CHANGELOG
Bugs
nicdex commentedon Feb 19, 2019
0.2.10 CHANGELOG
Bugs
can not read property debug of undefined#68 Merged PR Fix for issue #68 by using self._log_debug instead of this._log.debug #69 to fix a wrong usage of this in a function closure.nicdex commentedon May 20, 2019
0.2.11 CHANGELOG
Improvements
#73 move strict-event-emitter into regular dependencies
Bugs
#74 #75 #76 projections manager minor fixes
nicdex commentedon Aug 3, 2019
0.2.13 CHANGELOG
Bugs
#85 Fixed an issue where AppendToStream with expected version any and existing event did result in the event being saved. It was due to a protobufjs issue. Was fixed after updating it to latest version.
nicdex commentedon Nov 2, 2019
0.2.14 CHANGELOG
Bugs
#91 Isolate protobufjs library to work well with bad neighbor libraries
nicdex commentedon Nov 2, 2019
0.2.15 CHANGELOG
Bugs
nicdex commentedon Mar 2, 2020
0.2.16 CHANGELOG
Bugs
nicdex commentedon Sep 29, 2020
0.2.17 CHANGELOG
Bugs
nicdex commentedon Oct 2, 2020
0.2.18 CHANGELOG
Bugs