fix(deps): update dependency statsig-react to v2 #765
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^1.34.0
->^2.0.0
Release Notes
statsig-io/react-sdk (statsig-react)
v2.1.0
: - Update to use v5.1.0 of js clientCompare Source
Full Changelog: statsig-io/react-sdk@2.0.0...2.1.0
v2.0.0
: - Update to v5 of js client sdkCompare Source
Updates the react sdk to use version 5.0 of js sdk
Full Changelog: statsig-io/react-sdk@1.38.1...2.0.0
v1.38.1
: - Bugfix - memoization in SynchronousProviderCompare Source
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 theStatsigContext
to force anyone relying on this field to update their implementation due to these problems.Full Changelog: statsig-io/react-sdk@1.38.0...1.38.1
v1.38.0
: [release] 1.38.0 - queue events prior to initialization on StatsigCompare Source
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:
v1.37.1
: - bugfix: gate/config/experiment/layer result memoizationCompare Source
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
Full Changelog: statsig-io/react-sdk@1.37.0...1.37.1
v1.37.0
: - Add Support for Evaluation Callback OptionCompare Source
Adds a field to options which allows a function to be specified that will be called whenever a config is checked
Full Changelog: statsig-io/react-sdk@1.36.0...1.37.0
v1.36.0
: - Adds useFeatureGate hookCompare Source
Also bumps internal js sdk dependency
Full Changelog: statsig-io/react-sdk@1.35.0...1.36.0
v1.35.0
: - Support multi instanceCompare Source
Using https://github.com/statsig-io/js-client/releases/tag/4.45.1
StatsigClient
by caching including the sdk keyFull Changelog: statsig-io/react-sdk@v1.34.0...1.35.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.