v5.4.0

5.4.0 (2024-10-18)

Features

• Add support for client-side prerequisite events. (#112) (9d1708b)

5.3.0

5.3.0 (2024-06-18)

Features

• Add inExperiment to evaluation reason. (#105) (cf69770)
• Allow for synchronous inspectors. (#103) (7e490f4)

5.2.0

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

5.1.0

[5.1.0] - 2024-03-19

Changed:

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

Fixed:

• Pin dev version of node to compatible types.

Removed:

• HTTP fallback ping

5.0.3

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

5.0.2

[5.0.2] - 2023-02-15

Changed:

• Removed usage of optional chaining (?.) to improve compatibility with projects which are using older transpilation tooling.

5.0.1

[5.0.1] - 2023-01-10

Changed:

• Updated all types in typings.d.ts to be exported. This is to ensure that those types are included in generated documentation of dependent SDKs.

4.3.3

[4.3.3] - 2022-12-13

Fixed:

• Issue #84 Warning: Accessing non-existent property 'messages' of module exports inside circular dependency

5.0.0

[5.0.0] - 2022-11-30

This major version release of js-sdk-common corresponds to the upcoming releases of the js-client-sdk v3 and react-client-sdk v3, and cannot be used with earlier SDK versions.

Added:

• Replaced users with contexts. A context is a generalized way of referring to the people, services, machines, or other resources that encounter feature flags in your product. All methods which previously operated on LDUser now operate on LDContext.

Changed:

• LDClient.getUser has been replaced with LDClient.getContext.
• privateAttributeNames has been replaced with privateAttributes. Private attributes now allow using attribute references, which allow for marking nodes in nested JSON private.

Removed:

• Alias events are no longer supported and the alias method has been removed from LDClient.
• Support for the secondary attribute has been removed from LDUser. If a secondary attribute is included in a context, then it is a normal attribute that can be used in rule evaluation, but it will not affect bucketing.
• allowFrequentDuplicateEvents has been removed from LDOptions. This had been deprecated in a previous version. The default behavior is as if this option had been set to true.
• autoAliasingOptOut has been removed from LDOptions. This functionality has been superseded by multi-context support.
• inlineUsersInEvents has been removed from LDOptions. Changes associated with contexts has removed the needed for this option.

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.

4.3.2

[4.3.2] - 2022-10-20

Added:

• Implemented jitter and backoff for streaming connections. When a connection fails the retry will start at the streamReconnectDelay and will double on each unsuccessful consecutive connection attempt (backoff) to a max of 30 seconds. The delay will be adjusted from 50%-100% of the calculated delay to prevent many clients from attempting to reconnect at the same time (jitter).

Changed:

• Removed usage of flatMap. (Thanks @mateuszsikora)