docs: remove outdated caveat about useId in async Server Components#7865
docs: remove outdated caveat about useId in async Server Components#7865ohjooyeong wants to merge 1 commit intoreactjs:mainfrom
Conversation
|
Hi @ohjooyeong! Thank you for your pull request and welcome to our community. Action RequiredIn 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. ProcessIn 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 If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
|
It doesn't work if you do this: The error is in the linter only I believe. |
|
cc @eps1lon |
The previous documentation stated that useId cannot be used in Server Components that are async functions.
However, as of React 19.1.0, useId now works correctly in async Server Components as well.
I have tested this behavior and confirmed that the caveat is no longer necessary.
This PR removes the outdated note to reflect the current behavior.