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".

3.2.3

Diff

launchdarkly

published 3.2.3 • 5 years ago

Changelog

Source

[3.2.3] - 2020-03-06

Fixed:

At client initialization time, if the initial flag polling request failed, it would cause an unhandled promise rejection unless the application had called waitForInitialization() and provided an error handler for the promise that was returned by that method. While that is correct behavior if the application did call waitForInitialization() (any promise that might be rejected should have an error handler attached), it is highly undesirable if the application did not call waitForInitialization() at all-- which is not mandatory, since the application could use events instead, or waitUntilReady(), or might simply not care about waiting for initialization. This has been fixed so that no such promise is created until the first time the application calls waitForInitialization(); subsequent calls to the same method will return the same promise (since initialization can only happen once).
A bug in the event emitter made its behavior unpredictable if an event handler called on or off while handling an event. This has been fixed so that all event handlers that were defined at the time the event was fired will be called; any changes made will not take effect until the next event.

3.2.2

Diff

launchdarkly

published 3.2.2 • 5 years ago

Changelog

Source

[3.2.2] - 2020-02-13

Fixed:

When sending stream connection statistics in diagnostic event data, always specify the failed property even if it is false. This only affects LaunchDarkly's internal analytics.

3.2.1

Diff

launchdarkly

published 3.2.1 • 5 years ago

Changelog

Source

[3.2.1] - 2020-02-13

Fixed:

When using secure mode in conjunction with streaming mode, if an application specified a new hash parameter while changing the current user with identify(), the SDK was not using the new hash value when recomputing the stream URL, causing the stream to fail. (#13)

3.2.0

Diff

launchdarkly

published 3.2.0 • 5 years ago

Changelog

Source

[3.2.0] - 2020-02-12

Added:

The SDKs now periodically send diagnostic data to LaunchDarkly, describing the version and configuration of the SDK, the architecture and version of the runtime platform (provided by the platform-specific SDK packages), and performance statistics. No credentials, hostnames, or other identifiable values are included. This behavior can be disabled with the diagnosticOptOut option or configured with diagnosticRecordingInterval.

3.2.0-beta3

Diff

launchdarkly

published 3.2.0-beta3 • 5 years ago

3.2.0-beta2

Diff

launchdarkly

published 3.2.0-beta2 • 5 years ago

3.2.0-beta1

Diff

launchdarkly

published 3.2.0-beta1 • 5 years ago

3.1.2

Diff

launchdarkly

published 3.1.2 • 5 years ago

Changelog

Source

[3.1.2] - 2020-01-31

Removed:

Removed an unused dependency on @babel/polyfill. (Thanks, bdwain!)
Changed exact version dependencies to "highest compatible" dependencies, to avoid having modules that are also used by the host application loaded twice by NPM. (#8)

…

launchdarkly-js-sdk-common - npm Package Versions

3.2.5

.css-1z04cui{margin-bottom:var(--chakra-space-4);font-size:var(--chakra-fontSizes-md);}[3.2.5] - 2020-03-18

Fixed:

3.2.4

[3.2.4] - 2020-03-18

Fixed:

3.2.3

[3.2.3] - 2020-03-06

Fixed:

3.2.2

[3.2.2] - 2020-02-13

Fixed:

3.2.1

[3.2.1] - 2020-02-13

Fixed:

3.2.0

[3.2.0] - 2020-02-12

Added:

3.2.0-beta3

3.2.0-beta2

3.2.0-beta1

3.1.2

[3.1.2] - 2020-01-31

Removed:

[3.2.5] - 2020-03-18