Releases: daily-co/daily-react
Releases · daily-co/daily-react
0.5.0
Features
- 🆕
useTranscriptionhook: check our docs to learn when and how to use it.
Improvements
- Breaking:
useNetworknow returns'none'fortopologyuntil the network topology is defined. Previouslytopologydefaulted to'peer'which could lead to wrong assumptions when joining a call running in'sfu'mode. This change goes hand in hand with a fix indaily-js@0.31.0.
This release requires @daily-co/daily-js@0.31.0.
0.4.0
Maintenance
- Added
fs-extrain order to make autocompletion foruseParticipantProperty - Added listener to the
selected-devices-updatedevent to the useDevices hook - Fixed
daily-jstypes and type assumptions in daily-react-hooks tests. - Moved all state management from
useDevicesto a newDailyDeviceswrapper component, to reducedaily-jsAPIs being invoked from events - Refactored
useMediaStreamTrackstate selection - Improve the DX of the
useParticipantPropertyhook by making it return the exact type of property that we subscribed for and also allow to take multiple inputs - Improve typing for
useParticipantProperty DailyProviderNow cleans up inner callObject state, when callObject prop is destroyed or nullified- Bumped peerDependency on daily-js to 0.30.0
0.3.0
Features
- New hook
useLocalSessionId: This optimizes render cycles compared to callinguseLocalParticipantin order to get the local participant'ssession_id. We recommend migrating touseLocalSessionIdwhen only thesession_idis of interest in a component. - New hook
useParticipantProperty: This hook allows to subscribe to only a specific property for a specific participant, identified by theirsession_id. Similar touseLocalSessionIdthis hook allows to reduce re-render cycles when only a single, or small subset of participant properties are relevant to a component.
Maintenance
- Removed
babel-plugin-transform–regeneratorfrom our Babel config tounsafe-evalissues when usingdaily-react-hooksin a CSP-configured runtime environment. - Bumped peerDependency on daily-js to 0.29.0
0.2.6
Bugfixes
- Fixed an issue where
useLocalParticipant()did not return the correct participant object, after calling.leave()and.startCamera()afterwards.
0.2.5
Bugfixes
- Fixed a bug, where assigning an updated
callObjectinstance toDailyProviderwas not stored internally anduseDailywould still return the initialcallObjectinstance.
0.2.4
Improvements
useDevicesis now registering for the newavailable-devices-updatedevent to keep the list of media devices up to date- When switching to a different microphone via
setMicrophonefromuseDevicesthere won't be a camera blip anymore
Bugfixes
- Fixed
useLocalParticipantto stay synchronized withdaily.participants().local, even when leaving and joining a new meeting from the same callObject instance
Maintenance
- ESLint configuration updates
- Updated
peerDependencyon @daily-co/daily-js to 0.28.0
0.2.3
Bugfixes
- Fixed component types to be compatible with React 18
0.2.2
Improvements
useRoom()initializes room info with the [access-state-updated] (https://docs.daily.co/reference/daily-js/events/meeting-events#access-state-updated) event. This means full room information is available as soon as eitherpreAuth()orjoin()are called.useRoom()doesn't reset anymore when a meeting transitions to theleft-meetingmeeting state.
Bugfixes
- Fixed return type for
useRoom(). It is nowDailyRoomInfo | nullas intended since 0.2.0, notDailyPendingRoomInfo | DailyRoomInfo | nullas before 0.2.0.
0.2.1
Maintenance
- Fixed
peerDependenciesfor@daily-co/daily-jsandreactto allow a wider range of versions
0.2.0
Features
- useParticipantIds has new
'screen'filter to get participants with active screen shares
Improvements
- Reduced re-render cycles due to participant events
- Reduced re-render cycles by grouping multiple state updates into transactions
- Improved useRoom() to return meaningful room data as soon as possible
- Improved throttling in useThrottledDailyEvent
Maintenance
- Updated peerDependency recoil to 0.7.0