Stability of the useToast Beta version

[mikrojane]

Hello, my team is building a design system that often makes use of React Aria hooks, and we have found them very reliable and accessible – thank you for sharing all of your excellent work 🙇‍♂️

Next up in our backlog is a Toast component, and the useToast hook, along with the useToastState look very promising for what we were hoping to build. We are generally very cautious about v0 or beta dependencies though.

API changes may still occur in beta versions, however once in beta, this is less likely to happen. There may be outstanding features or issues in beta versions, which will be reported on GitHub.

That's reassuring, and I don't see many related issues reported yet.

I believe that since this beta feature is released in a separate @react-aria/[email protected] package, that if it is released in a future version of react-aria with breaking changes, then our component using the separate version will be unaffected even if we upgrade the core react-aria dependency?

I also see that the "RAC Toast" task was recently completed, suggesting a React Aria Components version of the Toast will be released very soon, and I presume it was built on the useToast hook – so the API is probably pretty stable, but are there any significant breaking changes expected that we can prepare for?

Thank you in advance for the insights!

[snowystinger]

Maybe hold off until our next release (hopefully next week). We're moving Toast along in the release cycle, including a RAC Toast as you noted. There were some changes as a result of this work. Mainly around the priority queue system (if you need this, it's now recommended to build that yourself).

You can get an idea of API changes looking at the relevant PRs #7805, #7631

This PR has a few more typescript diffs because of reasons, but the main thing is that there were no changes to the hooks in this one not already covered by the other two prs #7783 (the rest can be ignored if it isn't a toast related API)

We'll also have more information in the release notes once we're done.

Thanks for the patience and understanding.