launchdarkly-js-sdk-common - npm Package Versions

[3.3.0] - 2021-01-26

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.

[3.2.12] - 2021-01-25

Changed:

• When creating a stream connection, we now set a streamReadTimeoutMillis option which is hard-coded to the standard LaunchDarkly stream timeout of 5 minutes. This option is implemented by launchdarkly-eventsource 1.4.0 and higher, and should be ignored by SDKs that are not using that EventSource implementation.

[3.2.11] - 2020-11-17

Fixed:

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

[3.2.10] - 2020-09-14

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.

[3.2.9] - 2020-07-10

Fixed:

• Removed uses of String.startsWith that caused errors in Internet Explorer unless a polyfill for that function was present.

[3.2.8] - 2020-05-13

Fixed:

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

[3.2.7] - 2020-04-30

Fixed:

• Some diagnostic event data was being sent twice, resulting in extra HTTP requests. This did not affect analytics events, so customer data on the dashboard and in data export would still be correct.

[3.2.6] - 2020-03-31

Fixed:

• The default logging implementation (createConsoleLogger) could throw errors in Internet Explorer 11 if log output (of an enabled level) happened while the developer tools were not open. This is because in IE 11, the console object does not exist unless the tools are open. This has been fixed so the logger does not try to use console unless it currently has a value.