Releases: launchdarkly/react-client-sdk
Releases · launchdarkly/react-client-sdk
3.0.0
[3.0.0] - 2022-12-07
The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." For more information please read the JavaScript SDK's latest release notes.
For detailed information about this version, please refer to the list below. For information on how to upgrade from the previous version, please read the migration guide.
Added:
- The
context
provider configuration option has been added.
Fixed:
- We fixed a bug where using native Object functions on the flags proxy object results in errors. This was reported in issue #162.
Deprecated:
- The
user
provider configuration option has been deprecated. Please usecontext
instead.
2.29.3
2.29.2
[2.29.2] - 2022-10-28
Fixed:
- An issue with
asyncWithLDProvider
that was causing flags to be empty on first render.
2.29.1
[2.29.1] - 2022-10-21
Changed:
- Upgraded to
js-client-sdk
version2.24.2
which includes implementations ofjitter
andbackoff
for streaming connections. When a connection fails the retry will start at thestreamReconnectDelay
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
).
2.29.0
[2.29.0] - 2022-10-18
Changed:
- Updated
js-client-sdk
to2.24.0
which added support forInspectors
that can be used for collecting information for monitoring, analytics, and debugging.
2.28.0
[2.28.0] - 2022-10-05
Changed:
- Updated
js-client-sdk
version which removed event de-duplication functionality which was made redundant by support of summary events. This will improve the default event behavior when using experimentation.
2.27.0
[2.27.0] - 2022-08-31
Added:
useFlags
hook is now generically typed, allowing you to assert what type your flag set will be.useLDClientError
hook for exposing client initialization failures.
Changed:
sendEventsOnlyForVariation
is now set totrue
by default to prevent a flag evaluation event being generated for every flag on load.flags
object (that is either injected via props usingLDConsumer
or returned from theuseFlags
hook) will generate a flag evaluation event on flag read (using a JavaScript proxy). This can be disabled by settingreactOptions.sendEventsOnFlagRead: false
.- upgraded from ES5 to ES6.
2.26.0
[2.26.0] - 2022-04-27
Added:
LDOptions.application
, for configuration of application metadata that may be used in LaunchDarkly analytics or other product features. This does not affect feature flag evaluations.- Added
basicLogger
, a replacement for the deprecatedcreateConsoleLogger
.
Fixed:
- The
baseUrl
,streamUrl
, andeventsUrl
properties now work properly regardless of whether the URL string has a trailing slash. Previously, a trailing slash would cause request URL paths to have double slashes.
2.25.2
2.25.1
[2.25.1] - 2022-02-18
Fixed:
- If the SDK receives invalid JSON data from a streaming connection (possibly as a result of the connection being cut off), it now uses its regular error-handling logic: the error is emitted as an
error
event or, if there are noerror
event listeners, it is logged. Previously, the error would be thrown as an unhandled exception.