Releases: launchdarkly/js-client-sdk
Releases · launchdarkly/js-client-sdk
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
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
1.1.10
Added
- Add a warning when tracking unknown custom goal events
Changelog
1.1.8
Fixed
- Cached
localStorage
copy is not overwritten anymore when connection to LD fails
Changelog