James Burnside

> Thank you @JamesBurnside James Burnside FTE for checking the PR. For information, I did not get any changes after running `rush changelog`. It appears we have a bug in...

Thanks for your patience, the `rush changelog` command has now been fixed so you should be good to run and push the changefile to this PR. Can you also run...

> > @JamesBurnside Thanks for fixing the `rush changelog` command, I ran the command and pushed the changefile. Next, I ran the `rush build:all-flavors` command and unfortunately I got no...

Closing this issue as a hotfix has been released in 1.3.1, please create a new issue if you are still seeing this in `@azure/[email protected]`

Closing this due to inactivity. For reference, here is an example snippet of what @dmceachernmsft is referring to: ```tsx import { usePropsFor, VideoGallery } from '@azure/communication-react'; import React, { useMemo...

> PRs were just merged to update our peer deps @micahgodbolt thanks for making this change! When do you expect to do your next stable npm release with the update?

Thanks for this thread, we reduced our rush install time from ~56s to ~34s -- however is there any further caching that could reduce the 34s? What work is being...

Thanks for filing this issue, we'll take a look at this as soon as possible.

> How do you feel about holding this PR back until we cut the next stable release branch. It's been a while since the last stable release, and it'd be...

Hi @ricmeira, apologies for the delay, this error typically occurs if the stream becomes undefined. To enable us to help further we'll need a code snippet of how you are...