fix: post-review MessageReactionsDetail adjustments

[arnautov-anton]

Breaking Changes

Removed deprecated sortReactionDetails prop and ReactionDetailsComparator type

The sortReactionDetails prop has been removed from the following components and contexts:

• MessageProps (and by extension Message component)
• MessageContextValue (and by extension MessageContext)
• MessageReactionsProps (and by extension MessageReactions component)
• MessageReactionsDetailProps (and by extension MessageReactionsDetail component)
• MessageListProps (and by extension MessageList component)
• VirtualizedMessageListProps (and by extension VirtualizedMessageList component)

The ReactionDetailsComparator type export has been removed from src/components/Reactions/types.ts.

Migration: Replace all usages of sortReactionDetails with the reactionDetailsSort prop, which accepts a ReactionSort object (server-side sort) instead of a client-side comparator function.

Removed deprecated reaction_counts prop from MessageReactionsProps

The reaction_counts prop on MessageReactions has been removed. It was previously ignored at runtime.

Migration: Use reaction_groups instead, which provides richer per-reaction-type summary data (including count).

Removed deprecated reactionOptions prop from MessageReactionsProps

The reactionOptions prop on MessageReactions has been removed. The component now reads reactionOptions exclusively from ComponentContext.

Migration: Pass reactionOptions via <WithComponents overrides={{ reactionOptions }}>...</WithComponents> instead of directly on <MessageReactions>.

UseProcessReactionsParams no longer accepts reaction_counts or reactionOptions

The UseProcessReactionsParams type (used by the useProcessReactions hook) no longer includes reaction_counts or reactionOptions fields, consistent with the prop removals above.

New Features

capLimit prop on MessageReactions

A new optional capLimit prop allows configuring how many reaction types are displayed before overflow in each visual style:

capLimit?: {
  clustered?: number; // default: 5
  segmented?: number; // default: 4
};

Previously, only the segmented style (in top position) capped reactions at a hardcoded limit of 4. Now the clustered style also caps displayed reaction types (default: 5), and both limits are configurable.

reactionGroups added to useProcessReactions return value

The useProcessReactions hook now returns reactionGroups (the resolved Record<string, ReactionGroupResponse> | undefined) alongside the existing return fields.

reactionGroups prop on MessageReactionsDetail

MessageReactionsDetail now accepts a reactionGroups prop used to determine reaction counts when removing a reaction. This enables the component to switch to the "all reactions" view when the last reaction of a given type is removed, instead of attempting to refetch an empty list.

UseProcessReactionsParams type is now exported

The UseProcessReactionsParams type is now exported from src/components/Reactions/hooks/useProcessReactions.tsx, making it available for consumers who build custom reaction processing logic.

[github-actions]

Size Change: +119 B (+0.02%)

Total Size: 614 kB

📦 View Changed

Filename	Size	Change
dist/cjs/index.js	237 kB	+61 B (+0.03%)
dist/css/index.css	47.3 kB	-4 B (-0.01%)
dist/es/index.mjs	235 kB	+62 B (+0.03%)

ℹ️ View Unchanged

Filename	Size
dist/cjs/audioProcessing.js	1.32 kB
dist/cjs/emojis.js	2.96 kB
dist/cjs/mp3-encoder.js	1.27 kB
dist/cjs/WithAudioPlayback.js	42.1 kB
dist/css/emoji-replacement.css	456 B
dist/es/audioProcessing.mjs	1.31 kB
dist/es/emojis.mjs	2.47 kB
dist/es/mp3-encoder.mjs	756 B
dist/es/WithAudioPlayback.mjs	42 kB

_{compressed-size-action}

[stream-ci-bot]

🎉 This PR is included in version 14.0.0-beta.5 🎉

The release is available on:

• GitHub release
• npm package (@beta dist-tag)

Your semantic-release bot 📦🚀