launchdarkly-js-client-sdk - npm Package Versions

[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] - 2020-11-17

Fixed:

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

[2.18.2] - 2020-10-19

Changed:

• With goals that use substring or regex mode for URL matching, the SDK previously was not able to match anything in a URL's hash fragment. Since some applications use path-like hash fragments (http://example.com/url/path#/additional/path), the SDK now considers any hash string that contains a slash to be part of the URL for matching purposes, if the matching mode is substring or regex. Hash strings that do not contain a slash are assumed to be simple HTML anchors and are not included in matching.

[2.18.1] - 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.

[2.18.0] - 2020-07-16

Added:

• Configuration option disableSyncEventPost, for preventing the SDK from trying to do a synchronous HTTP request to deliver analytics events while the page is closing. Such requests are not supported in current versions of Chrome, and although the SDK uses browser detection to avoid doing them if they are not supported, the browser detection mechanism does not work in some test environments.

[2.17.6] - 2020-07-13

Fixed:

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

[2.17.5] - 2020-05-13

Fixed:

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

[2.17.4] - 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.

[2.17.3] - 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.
• Updated some dependency versions to resolve a security vulnerability in the transitive acorn dependency. This dependency is only used for development and as a result the security vulnerability did not affect customers.

[2.17.2] - 2020-03-18

Fixed:

• Some users reported an error where the SDK said that the content type of a response was application/json, application/json; charset=utf8. It is invalid to have multiple Content-Type values in a response and the LaunchDarkly service does not do this, but an improperly configured proxy/gateway might add such a header. Now the SDK will tolerate a value like this as long as it starts with application/json. (#205)
• Fixed incorrect usage of Object.hasOwnProperty which could have caused an error if a feature flag had hasOwnProperty as its flag key.