5.2.3

Added

• abTastyOnTriggerRender global handler: A global callback abTastyOnTriggerRender is now
  registered on globalThis, allowing the AB Tasty QA tool to programmatically trigger flag re-fetches or
  force a re-render of flagged components without relying solely on DOM events.

Improved

• Dependency update: @flagship.io/js-sdk updated to 5.2.0.

5.2.2

Fixed

• Fixed useFlagship() hook flagsStatus object mutation issue that prevented React's useEffect from detecting changes. The flagsStatus object's properties (status, reason) were being mutated in place rather than creating a new object reference, causing React's shallow comparison in dependency arrays to fail. The object now returns a new reference when inner values change, ensuring proper reactivity.

5.2.1

Fixed

• Segment hit collection: Resolved API format issue in bucketing mode where context values weren't properly serialized as strings, causing hits to be rejected by the collection endpoint

5.2.0

Added

• FlagshipProviderSSR: A specialized provider component designed for server-side rendering environments, particularly optimized for Next.js 13+ applications using the App Router architecture.

  • Prevents hydration mismatches between server and client renders
  • Features default fetchNow: false configuration to better control flag fetching timing
  • Fully compatible with ESM imports
  • Simplifies flag management in modern React server components
  • Includes comprehensive TypeScript typings for improved developer experience

• Edge Runtime Support: New dedicated Edge bundle available for deploying in edge computing environments

  • Access via import from @flagship.io/react-sdk/edge
  • Optimized for edge runtimes like Vercel Edge Functions and Cloudflare Workers
  • Enhances global performance with reduced latency for flag evaluations
  • Fully compatible with Next.js Edge Runtime

Improved

• ESM Support: Enhanced module resolution with proper ESM/CommonJS detection
• Type System: Refined TypeScript type definitions for better developer experience

5.1.1

Fixed

• Error Handling — Fixed an issue in the troubleshooting hit system where an undefined error would occur during hit construction when fetchFlags failed
• QAA — Fixed an issue where targeting campaigns weren't properly displayed in QAA when campaign data was provided during visitor creation but no subsequent fetchFlags call was made. This ensures that QA testing works correctly regardless of initialization sequence.

5.1.1-beta.1

Fixed

• Error Handling — Fixed an issue in the troubleshooting hit system where an undefined error would occur during hit construction when fetchFlags failed

5.1.0

Added

• Shared Visitor ID with AB Tasty — The SDK can now share the same visitor ID with AB Tasty Tag, providing a consistent visitor experience across platforms.

Fixed

• ViteJS Dynamic Import Handling — Fixed an issue where ViteJS incorrectly interpreted JavaScript dynamic import statements in the Flagship SDK.

5.0.1

Fixed

• Qa Assistant issue on live campaigns

5.0.0

We're excited to announce Flagship SDK v5.0.0, featuring significant improvements in performance, capabilities, and developer experience across all supported runtime environments.

Added

• Emotion AI Integration — Utilize powerful emotion analysis capabilities to understand user reactions and tailor experiences based on emotional responses, enabling more empathetic and responsive applications.
• Shared Action Tracking — Seamlessly track user interactions between the web SDK and tag implementations with our new unified tracking system.
• Batch Limit for Activate Hits — Implemented a fixed maximum limit on activate hits per batch, significantly reducing network overhead while maintaining analytics accuracy.

Improved

• Enhanced Tree Shaking — Reduced bundle size through improved code splitting and dependency management, ensuring you only load what you need for your specific implementation.

Changed

• Contextual Segment Hits — In bucketing mode, segment hits are now only sent when the visitor context has been updated, reducing unnecessary network requests and improving performance.
• Naming Clarity — Renamed FetchFlagsStatus to FlagsStatus for improved API clarity and consistency throughout the SDK.

For migration assistance and detailed documentation, please refer to our official documentation.

4.1.0-beta.0

Add

• Emotion AI
• Limit the maximum number of activate hits per batch

Change

• The Flagship.start method is now asynchronous
• Segment hits in bucketing can be sent only when the visitor context has been updated