1.6.1

Fixed

• The SDK now polls the URL for changes if (and only if) there are page view goals, to ensure it is accurately reporting page views.

Changelog

1.6.0

[1.6.0] - 2018-03-28

Changed

• Added support for a future update to LaunchDarkly that will deliver individual feature flag changes over the streaming connection as they occur, rather than requiring the client to re-request all flags for each change.

1.5.2

Added

• The new flush method on the client object tells the client to deliver any stored analytics events as soon as possible, rather than waiting for the regularly scheduled event-flushing interval.

Fixed

• Fixed a bug that could prevent events from being generated for page view goals.

Changelog

1.5.1

[1.5.1] - 2018-03-07

Fixed

• Removed usage of the const keyword, to maintain IE10 compatibility. (Thanks, turnerniles!)

1.5.0

[1.5.0] - 2018-03-05

Added

• The options object now supports a samplingInterval property. If greater than zero, this causes a fraction of analytics events to be sent to LaunchDarkly: one per that number of events (pseudo-randomly). For instance, setting it to 5 would cause 20% of events to be sent on average.

1.4.0

Added

• The SDK now supports multiple environments. Calling initialize returns a new client each time.

Fixed

• The waitUntilReady Promise will now resolve even after the ready event was emitted — thanks @rmanalan!

Changelog

1.3.1

Fixed

• Methods that expose a Promise interface now properly return the resolution or rejection value to the caller.

Changelog

1.3.0

Added

• Support for private user attributes.
• New sendEvents option to control whether the SDK should send events back to LaunchDarkly or not. Defaults to true.
• It is now possible to wait for SDK readiness using waitUntilReady which returns a Promise. identify also returns a Promise (while still supporting the callback argument), which should make
  it easier to integrate into code that relies heavily on Promise's for asynchronous code.

Changed

• The SDK now respects the user's do-not-track setting

Changelog

1.2.0

[1.2.0] - 2017-12-15

Added

• Added useReport initialization option to use REPORT instead of GET when communicating with LaunchDarkly.

Fixed

• Authentication errors will now be logged — the root cause for these errors is usually an invalid client-side ID.

Changelog

1.1.13

[1.1.13] - 2017-12-12

Changed

• Emit an error event — separately from the ready event — in case fetching initial data fails. This allows consumers to respond accordingly.

Changelog