@frigade/react@2.10.3

Patch Changes

• e5c3939: Bump @frigade/js to ^0.9.7 to include the fix for sending STARTED_STEP events when completing a step.

@frigade/js@0.9.7

Patch Changes

• 2723c81: Send STARTED_STEP event for the next step when completing/skipping a step. Previously, complete() and skip() optimistically marked the next step as started in local state but did not send the STARTED_STEP event to the API, which caused a subsequent start() call to no-op.

@frigade/react@2.10.2

Patch Changes

• 2ed000b: Fix race conditions in JS SDK Flows
• Updated dependencies [2ed000b]
  • @frigade/js@0.9.6

@frigade/js@0.9.6

Patch Changes

• 2ed000b: Fix race conditions in JS SDK Flows

@frigade/react@2.10.1

Patch Changes

• d600eee: Fixes an issue related to form type select/multiple

@frigade/react@2.10.0

Minor Changes

• 11f71d9: Fixes an issue with Frigade and Vite

@frigade/react@2.9.6

Patch Changes

• 8496a7f: Fixes an issue where navigation change events were not firing in Firefox
• Updated dependencies [8496a7f]
  • @frigade/js@0.9.5

@frigade/js@0.9.5

Patch Changes

• 8496a7f: Fixes an issue where navigation change events were not firing in Firefox

@frigade/react@2.9.5

Patch Changes

• 75a5475: Adds an additional null check to Flows served through collections

@frigade/react@2.9.4

Patch Changes

• e1688af: - Fixes a bug where frigade.on('step.compelte') could sometimes be called for already completed steps in flows.
  • Fixes an issue with using Storybook with Frigade components
• Updated dependencies [e1688af]
  • @frigade/js@0.9.4