-
Notifications
You must be signed in to change notification settings - Fork 172
[Feature Request]: Support for React Server Components #1106
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
As far as I understand, server components is an experimental technology and the API is not stable yet (if there is a stable API, please provide a link). We do not support experimental technologies. If you want to experiment with this technology, you can make necessary patches locally. |
After further investigation, yes the technology is still experimental, my bad. Sorry about that 😶 |
Thanks for checking! I will resolve the issue for now, but feel free to reopen if there are any news on it |
Would you consider reopening this ticket now that RSC are stable? |
I am not sure the original ask to blindly add |
I've spun up a new issue to request adding |
Description
Hi everyone! 👋🏻
It would be a great move for Cloudscape components to support the (not so) new React Server Module Conventions v2. Many frameworks are now following this convention, making it difficult to use the components in an optimized way.
Quick fix (but not optimized)
At the moment, a simple hack is to create the following file and update your pages' imports. It makes all components 'Client Components', and should only be used as for compatibility issues. It will not make Cloudscape component 'Server Components'.
Click to reveal
Code of Conduct
The text was updated successfully, but these errors were encountered: