1.7.0

[1.7.0] - 2022-10-21

Changed:

• Updated launchdarkly-js-sdk-common to version 3.8.3.
• Updated launchdarkly-js-client-sdk to version 2.24.2.
• Updated launchdarkly-eventsource to version 1.4.4.

1.6.3

[1.6.3] - 2021-06-10

Fixed:

• Updated transitive dependency on the package url-parse due to a vulnerability warning.

1.6.2

[1.6.2] - 2021-06-09

Fixed:

• Events for the LaunchDarkly debugger are now properly pre-processed to omit private user attributes, as well as enforce only expected top level attributes are sent.
• Events for the LaunchDarkly debugger now include the index of the variation responsible for the evaluation result.

1.6.1

[1.6.1] - 2021-04-05

Fixed:

• The property LDOptions.inlineUsersInEvents was not included in the TypeScript definitions.

1.6.0

[1.6.0] - 2021-01-27

Added:

• Added the alias method. This method can be used to associate two user objects for analytics purposes. When invoked, this method will queue a new alias event to be sent to LaunchDarkly.
• Added the autoAliasingOptOut configuration option. This can be used to control the new automatic aliasing behavior of the identify method; by passing autoAliasingOptOut: true, identify will not automatically generate alias events.

Changed:

• The identify method will now automatically generate an alias event when switching from an anonymous to a known user. This event associates the two users for analytics purposes as they most likely represent a single person.

1.5.8

[1.5.8] - 2021-01-26

Changed:

• In streaming mode, the SDK now automatically drops and restarts the stream connection if it has received no data from the server within a 5-minute interval. This ensures that if the connection fails in such a way that the SDK cannot detect the failure as an I/O error, it will not hang forever waiting for updates from the phantom connection. The LaunchDarkly streaming service sends a tiny "heartbeat" message at regular intervals less than this timeout, to ensure that the SDK will not drop the connection if it is still usable. This logic exists in most other LaunchDarkly SDKs but was not previously implemented in the Electron SDK.

1.5.7

[1.5.7] - 2020-11-17

Fixed:

• Updated the LDEvaluationDetail.reason type definition to be nullable. This value will be null when LDOptions.evaluationReasons is false.

1.5.6

[1.5.6] - 2020-09-14

Changed:

• The SDK's CircleCI configuration now tests compatibility against each supported major Electron version, currently Electron 2 through 9.

Fixed:

• In streaming mode, when connecting to the Relay Proxy rather than directly to the LaunchDarkly streaming service, if the current user was changed twice within a short time it was possible for the SDK to revert to flag values from the previous user.

1.5.5

[1.5.5] - 2020-07-02

Changed:

• The default implementation of logging now uses Winston 3.x rather than Winston 2.x. This does not change the content of the log output, and if you have specified your own custom logger then the SDK still uses that. The only effect is that the SDK no longer has dependencies on Winston 2.x.

Fixed:

• Fixed a bug that could cause extra delays when receiving a large streaming update. The process will still be blocked for some amount of time as the JSON data is being parsed, which is unavoidable in the current architecture, but this bug made it block for longer than necessary.

1.5.4

[1.5.4] - 2020-05-13

Fixed:

• The TypeScript declaration for track() was missing the optional metricValue parameter.