Releases: statsig-io/react-sdk
2.1.0 - Update to use v5.1.0 of js client
- update to v5.1.0 of js client
Included In This Release
- 27c63ee kat-statsig
- bump js version (#185)
Full Changelog: 2.0.0...2.1.0
2.0.0 - Update to v5 of js client sdk
Updates the react sdk to use version 5.0 of js sdk
Included In This Release
Full Changelog: 1.38.1...2.0.0
1.38.1 - Bugfix - memoization in SynchronousProvider
We introduced a fix in 1.37.1 to memoize configs for the same update time. We cannot memoize on the config update time, because it is both 1) not set on server sdks when generating the initialize values, and 2) not an exhaustive memoization key. Instead, we stringify the initializeValues as the memoization key.
This update renames initValuesTime
in the StatsigContext
to force anyone relying on this field to update their implementation due to these problems.
Included In This Release
- ed06b9e tore-statsig
- bugfix: memoization in SynchronousProvider (#175)
Full Changelog: 1.38.0...1.38.1
[release] 1.38.0 - queue events prior to initialization on Statsig
Due to the order of effects, the effect to initialize Statsig was not actually called until child components rendered. This means that if you did not waitForInitialization or waitForCache, it would be possible to call methods on the Statsig class before it was initialized. Our gate/config/experiment and even event logging hooks were okay, because they consume the StatsigContext and guard on initialization being called.
This updates logevent to:
- not throw
- batch up to 20 events pre initialize (and then log them once the internal js sdk instance is ready to consume them). Note that it currently drops any additional events after 20 queued events.
Included In This Release
1.37.1 - bugfix: gate/config/experiment/layer result memoization
Memoization logic on hooks was broken due to object parameters changing references on rerenders.
This was masking another issue in the StatsigSynchronousProvider where we did not memoize on a new version of config specs passed in to the StatsigSynchronousProvider. Because we weren't memoizing, the results were correct, but the performance was degraded in this case as well.
Performance of hooks via both providers should be improved as a result
Updated statsig-js to 4.51.0
Included In This Release
Full Changelog: 1.37.0...1.37.1
1.37.0 - Add Support for Evaluation Callback Option
Adds a field to options which allows a function to be specified that will be called whenever a config is checked
Updated statsig-js to 4.50.1
Included In This Release
- 71ea87c sroyal-statsig
- Evaluation Callback (#163)
Full Changelog: 1.36.0...1.37.0
1.36.0 - Adds useFeatureGate hook
1.35.0 - Support multi instance
Using https://github.com/statsig-io/js-client/releases/tag/4.45.1
- Supports multiple instances of the
StatsigClient
by caching including the sdk key - internal diagnostics updates
Included In This Release
- 38ce204 sroyal-statsig
- Use Exact JS SDK Version (#156)
Full Changelog: v1.34.0...1.35.0
v1.34.0 - Update to use latest JS SDK
v1.33.0 - Expose StatsigOptions.gateEvaluationCallback
- Exposes the GateEvaluationCallback from statsig-js to the statsig-react SDK
- Fixes a race condition in the RN support where StableID might not have been loaded during an /initialize request
Updated statsig-js to 4.42.2
Included In This Release
Full Changelog: v1.32.0...v1.33.0