Future of the library?

[AndrewCraswell]

I'm curious what the future of this package is, now that TeamsFx has taken a peer dependency on this. It feels awkward that to use the official Microsoft TeamsFx React SDK, this package needs to be installed in parallel. There's also numerous places now that the Microsoft Docs reference this, although the ownership and maintenance of the project is not clear, since it's not hosted within the Microsoft Github organization. I think this hurts consumer trust, as there may be some relcutance to take a dependency.

Any chance TeamsFx could just own this package, and the API could become part of TeamsFx?? Seems like transitioning this package to an officially supported Microsoft package backed by a team that already depends on it might be the best fit. A similar thing happened with the unofficial MSAL React library, which transitioned to the MSAL team's ownership.

[wictorwilen]

Thanks for chiming in @AndrewCraswell - The TeamsFx team has removed the dependency on this library and essentially made a copy of it (with less functionality).

[AndrewCraswell]

Has that been committed yet? I'm still seeing dependencies in the TeamsFx React SDK:
https://github.com/OfficeDev/TeamsFx/blob/dev/packages/sdk-react/package.json

[wictorwilen]

Here's the PR for it: OfficeDev/microsoft-365-agents-toolkit#4989

[AndrewCraswell]

Got it. Looks like that hasn't trickled through all the libraries yet. My understanding is that now the Teamsfx React SDK needs to start using their own implementation, which hasn't happened yet