Enhance documentation on using Promises in Client Components with use

[MaxwellCohen]

This commit adds guidelines regarding the caching and stability of Promises passed to the use API in Client Components. It includes examples that demonstrate how to cache Promises to prevent components from resuspending on every render, and how to avoid pitfalls when using uncached or chained Promises.

If there are any changes wanted, I will gladly make them, or if this is not wanted, feel free to close this PR

AI transparancy notice: I leveraged Cursor auto AI to help write these changes

This is how I would resolve Issue #8290

[meta-cla]

Hi @MaxwellCohen!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[github-actions]

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[meta-cla]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!