Skip to content

3.2.0 fix <FlagsmithProvider /> initialisation

Choose a tag to compare

@kyle-ssg kyle-ssg released this 24 Jun 13:40
· 436 commits to main since this release

Prior to this release, flagsmith would initialise inside a useEffect within the FlagsmithProvider component, now it will initialise immediately as can be seen here. Initialising flagsmith asynchronously meant that the UI could flicker when default values are supplied, as well as being overall slower than it needs to be.

Thanks to @briangorham for spotting this 🚀 .