build(deps): bump flagsmith from 3.21.0 to 4.0.2

[dependabot]

Bumps flagsmith from 3.21.0 to 4.0.2.

Release notes

Sourced from flagsmith's releases.

Version 4.0.2

What's Changed

• fix: clear traits when identifying over previous identity by @​kyle-ssg in Flagsmith/flagsmith-js-client#229

Full Changelog: Flagsmith/flagsmith-js-client@4.0.1...4.0.2

v4.0.1 Fix onChange Generic Types

Closes Flagsmith/flagsmith-js-client#224

v4.0.0 - add list of changed flags/traits, improve resolve/reject of init

This will be the first version compatible with OpenFeature. Merges Flagsmith/flagsmith-js-client#223

Breaking changes

• Init will now reject if:
  • No environment ID is provider
  • Fetch fails and there's no cache (Init resolves on cache)
  • There's no cache/defaults and preventFetch is true
• The boolean properties traitsChange and flagsChanged are now a string[] of changed keys or null. This reduces breaking changes since falsey and truthy checks will still behave as before.

Other changes

• Init is (finally) async/await
• Init code is reduced by pulling out isolated functions
• Added tests around init promises
• Organised util files

3.24.0 - Read cache synchronously

Closes Flagsmith/flagsmith-js-client#222

The SDK will now synchronously read cache rather than fetching it asynchronously.

3.23.2 - Remove busy logs, fix onChange event

Merges Flagsmith/flagsmith-js-client#207 Closes Flagsmith/flagsmith-js-client#217

3.23.1 - Prevent Nextjs caching behaviour

Merges Flagsmith/flagsmith-js-client#216

3.23.0 - Fix missed events in useFlags

Closes Flagsmith/flagsmith-js-client#214

• Fixes flag updates from useFlags
• Fixes flag updates where flagsmith.init is not called

3.22.1 - Support fallback for non-JSON evaluations

Merges Flagsmith/flagsmith-js-client#213, thanks to @​levrik

3.22.0 - Prevent race condition between identify/getFlags

Prior to this release, clients that request identified/unidentified flags simultaneously could see the wrong results due to a race condition. Although this signifies incorrect usage of the SDK, this will no longer occur.

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)