2.21.0

[2.21.0] - 2022-03-21

Added:

• Added basicLogger, a replacement for the deprecated createConsoleLogger.

2.20.2

[2.20.2] - 2022-02-18

Fixed:

• If the SDK receives invalid JSON data from a streaming connection (possibly as a result of the connection being cut off), it now uses its regular error-handling logic: the error is emitted as an error event or, if there are no error event listeners, it is logged. Previously, the error would be thrown as an unhandled exception.

2.20.1

[2.20.1] - 2022-02-02

Fixed:

• If the browser local storage mechanism throws an exception (for instance, if it is disabled or if storage is full), the SDK now correctly catches the exception and logs a message about the failure. It will only log this message once during the lifetime of the SDK client. (#54)

2.20.0

[2.20.0] - 2021-10-15

Added:

• New property LDOptions.requestHeaderTransform allows custom headers to be added to all HTTP requests. This may be necessary if you have an Internet gateway that uses a custom header for authentication. Note that custom headers may cause cross-origin browser requests to be rejected unless you have a way to ensure that the header name also appears in Access-Control-Allow-Headers for CORS preflight responses; if you are connecting to the LaunchDarkly Relay Proxy, it has a way to configure this.

2.19.4

[2.19.4] - 2021-10-12

Fixed:

• Removed an obsolete warning that would appear in the browser console after calling track: Custom event "_____" does not exist. Originally, the SDK had an expectation that track would be used only for event keys that had been previously defined as custom goals in the LaunchDarkly dashboard. That is still often the case, but it is not required and LaunchDarkly no longer sends custom goal names to the SDK, so the warning was happening even if such a goal did exist.

2.19.3

[2.19.3] - 2021-10-12

This release is broken and cannot be used.

2.19.2

[2.19.2] - 2021-06-08

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.

2.19.1

[2.19.1] - 2021-04-01

Fixed:

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

2.19.0

[2.19.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.

2.18.3

[2.18.3] - 2020-11-17

Fixed:

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