Skip to content

v1.1.0

Compare
Choose a tag to compare
@dferber90 dferber90 released this 06 Oct 08:51
· 76 commits to master since this release
90a6f28

This release adds the ability to specify a timeout for loading flags on the server. Flags usually resolve within ~75ms, but in case something goes wrong the flag evaluation requests can now be aborted at a user-configured timeout.

The configuration option can be set globally in configure() for clientLoadingTimeout, serverLoadingTimeout and staticLoadingTimeout each.

The global configuration can be overwritten per page by useFlags and getFlags by specifying the loadingTimeout option.

Adds

  • config.clientLoadingTimeout: The timeout used by useFlags on the client
  • config.serverLoadingTimeout: The timeout used by getFlags inside of getServerSideProps (for server-side rendering)
  • config.staticLoadingTimeout: The timeout used by getFlags inside of getStaticProps or getStaticPaths (for static site generation)

Deprecates

  • configure({ loadingTimeout }). Use configure({ clientLoadingTimeout }) instead. It behaves the same, it was renamed only.

Full Changelog: v1.0.2...v1.1.0