1.7.4

[1.7.4] - 2018-05-23

Fixed

• Fixed a bug that caused events not to be sent if options.sendEvents was explicitly set to true.
• HTTP requests will no longer fail if there is a charset specified in the response's Content-Type header. (#87)

1.7.3

[1.7.3] - 2018-05-08

Fixed

• The client no longer creates an empty XMLHttpRequest at startup time (which could interfere with unit tests).

1.7.2

[1.7.2] - 2018-05-07

Fixed

• The client no longer creates an empty XMLHttpRequest at startup time (which could interfere with unit tests).

1.7.0

Changed

• The build now uses Rollup, Babel and Jest.

Fixed

• Fixed a bug that caused a syntax error when running in Internet Explorer 11.
• Fixed an IE 11 incompatibility in the example page index.html.
• Fixed a bug that caused the SDK to send events on beforeunload even if it should not send events.

Changelog

1.6.2

Fixed

• LDClient.track properly sets the user for custom events.

Changelog

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.