launchdarkly-js-client-sdk - npm Package Versions

3.5.0 (2024-10-18)

Features

• Add support for client-side prerequisite events. (#306) (fe51da0)

[3.4.0] - 2024-06-20

Changed:

• Updated to launchdarkly-js-sdk-common 5.3.0 which supports synchronous inspectors.

[3.3.0] - 2024-05-01

Added:

• Added an optional timeout to the waitForInitialization method. When a timeout is specified the returned promise will be rejected after the timeout elapses if the client has not finished initializing within that time. When no timeout is specified the returned promise will not be resolved or rejected until the initialization either completes or fails.

Changed:

• The track method now validates that the provided metricValue is a number. If a metric value is provided, and it is not a number, then a warning will be logged.

Fixed:

• Fixed the documentation for evaluationReasons for the identify method.

[3.2.0] - 2024-03-19

Changed:

• Redact anonymous attributes within feature events
• Always inline contexts for feature events

[3.1.4] - 2023-09-06

Fixed:

• #283 Catch xhr errors on page close and ignore them to reduce noise.

[3.1.3] - 2023-04-12

Fixed:

• Fixed an issue that was preventing page view/click events from being sent. (Thanks, seanr-cardless!)

[3.1.2] - 2023-03-21

Changed:

• Update LDContext to allow for key to be optional. This is used when making an anonymous context with a generated key.

[3.1.1] - 2023-02-15

Changed:

• Upgrade to js-sdk-common version 5.0.2. This removes usage of optional chaining (?.) to allow for use with older transpilers.

[3.1.0] - 2023-01-18

Changed:

• Changed event flushing on page close to be based on page visibility. This should increase compatibility with the bfcache.
• Updated launchdarkly-js-sdk-common to version 5.0.1 for improved documentation generation.

[3.0.0] - 2022-12-07

The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."

For detailed information about this version, please refer to the list below. For information on how to upgrade from the previous version, please read the migration guide.

Added:

• The types LDContext, LDSingleKindContext, and LDMultiKindContext define the new "context" model.
• All SDK methods that took an LDUser parameter now take an LDContext. LDUser is now a subset of LDContext, so existing code based on users will still work.

Changed (breaking changes from 3.x):

• There is no longer such a thing as a secondary meta-attribute that affects percentage rollouts. If you set an attribute with that name in LDContext, it will simply be a custom attribute like any other.
• Evaluations now treat the anonymous attribute as a simple boolean, with no distinction between a false state and an undefined state.
• LDClient.getUser has been replaced with LDClient.getContext.
• privateAttributeNames has been replaced with privateAttributes in LDOptions. Private attributes now allow using attribute references.

Changed (behavioral changes):

• Analytics event data now uses a new JSON schema due to differences between the context model and the old user model.

Removed:

• Removed all types, fields, and methods that were deprecated as of the most recent 3.x release.
• Removed the secondary meta-attribute in LDUser.
• The alias method no longer exists because alias events are not needed in the new context model.
• The autoAliasingOptOut and inlineUsersInEvents options no longer exist because they are not relevant in the new context model.

Deprecated:

• The LDUser object has been deprecated. Support for LDUser is maintained to simplify the upgrade process, but it is recommended to use LDContext in the shape of either LDSingleKindContext or LDMultiKindContext.